super(false, true, true, true);
  }

  @Override
  Table<String, Integer, Character> makeTable() {
    Table<String, Integer, String> original = HashBasedTable.create();
    return transformValues(original, TableCollectionTest.FIRST_CHARACTER);
  }

  @Override
  protected Map<String, Map<Integer, Character>> makePopulatedMap() {
    Table<String, Integer, String> table = HashBasedTable.create();

    Set<Character> positive = Sets.newHashSetWithExpectedSize(chars.length);
    for (char c : chars) {
      positive.add(c);
    }
    for (int c = 0; c <= Character.MAX_VALUE; c++) {
      assertFalse(positive.contains(Character.valueOf((char) c)) ^ m.matches((char) c));
    }
  }

  static char[] randomChars(Random rand, int size) {
    Set<Character> chars = new HashSet<>(size);

    the timeouts manually.

 *  **OkHttp now rejects request headers that contain invalid characters.** This
    includes potential security problems (newline characters) as well as simple
    non-ASCII characters (including international characters and emoji).

 *  **Call canceling is more reliable.**  We had a bug where a socket being

        // Execute the job
        String result = purgeDocJob.execute();

        // Assert deleteByQuery was called with special characters
        assertTrue(deleteByQueryCalled);
        assertEquals("fess.update-index$special%chars", deleteIndex);

        // Assert field name with special characters was used
        assertNotNull(deleteQuery);
        assertTrue(deleteQuery instanceof RangeQueryBuilder);

        // Should handle special characters properly
        assertTrue(written > specialPath.length());

        // Check information level
        int actualInfoLevel = SMBUtil.readInt2(buffer, 0);
        assertEquals(0x0101, actualInfoLevel);
    }

    @Test
    void testWriteParametersWithUnicodePath() {
        String unicodePath = "test/文件名.txt"; // Chinese characters

		HTTPStatusCode: http.StatusBadRequest,
	},
	ErrInvalidEncryptionKeyID: {
		Code:           "InvalidRequest",
		Description:    "The specified KMS KeyID contains unsupported characters",
		HTTPStatusCode: http.StatusBadRequest,
	},
	ErrInsecureSSECustomerRequest: {
		Code:           "InvalidRequest",

        assertEquals(message, exception.getMessage());
        assertNull(exception.getCause());
    }

    public void test_constructor_withSpecialCharacters() {
        // Test with special characters in message
        String message = "Search not supported: \n\t!@#$%^&*(){}[]|\\:;\"'<>,.?/~`";
        UnsupportedSearchException exception = new UnsupportedSearchException(message);

    }

    /**
     * Determines the character set for the given file.
     * Currently returns the default charset configured for this client.
     *
     * @param file The file to determine the charset for
     * @return The character set name
     */
    protected String getCharSet(final File file) {
        return charset;
    }

    /**
     * Gets the character encoding used for FTP operations.
     *

/**
 * Tests {@link SingletonImmutableTable}.
 *
 * @author Gregory Kick
 */
@GwtCompatible
@NullMarked
public class SingletonImmutableTableTest extends AbstractImmutableTableTest {
  private final ImmutableTable<Character, Integer, String> testTable =
      new SingletonImmutableTable<>('a', 1, "blah");

  public void testHashCode() {
    assertEquals(Objects.hash('a', 1, "blah"), testTable.hashCode());
  }

        assertNull(exception.getCause());
    }

    public void test_constructor_withSpecialCharacters() {
        // Test with username containing special characters
        String username = "******@****.***";
        FessUserNotFoundException exception = new FessUserNotFoundException(username);

        assertNotNull(exception);