Did you *actually* encounter the need for this enhancement in a real-world scenario, or does
        it just seem like a sensible behavior for the feature to have?


        Before we make significant changes to existing features in Guava, we really want to be sure
        that it's for a use case that actually comes up in the real world. We want to hear the
        real-world use case so the community can discuss and debate whether this feature is actually

    val responseString = decompressed.body.string()
    assertThat(responseString).isEqualTo("hello zstd world")
  }

  @Test
  fun testDecompressGzip() {
    val s = "hello gzip world".encodeUtf8().gzipCompress()

    val response =
      response("https://example.com/", s) {
        header("Content-Encoding", "gzip")
      }

    }
  }

  @Test
  fun singlePart() {
    val expected =
      """
      |--123
      |
      |Hello, World!
      |--123--
      |
      """.trimMargin().replace("\n", "\r\n")
    val body =
      MultipartBody
        .Builder("123")
        .addPart("Hello, World!".toRequestBody(null))
        .build()
    assertThat(body.boundary).isEqualTo("123")

        }
    }

    public void test_startProcess_withBufferSizeAndCallback() {
        String sessionId = "test_session_buffer";
        List<String> cmdList = Arrays.asList("echo", "hello world");
        Consumer<ProcessBuilder> pbCall = pb -> {
            pb.redirectErrorStream(true);
        };

        List<String> outputs = new ArrayList<>();

        assertEquals("hello", DocumentUtil.encodeUrl("hello"));
        assertEquals("hello-world", DocumentUtil.encodeUrl("hello-world"));
        assertEquals("hello_world", DocumentUtil.encodeUrl("hello_world"));
        assertEquals("hello.world", DocumentUtil.encodeUrl("hello.world"));
    }

    public void test_encodeUrl_empty_and_null() {
        assertEquals("", DocumentUtil.encodeUrl(""));

  }

  @Test
  fun write() {
    val operator =
      FileOperator(
        randomAccessFile!!.getChannel(),
      )
    val buffer1 = Buffer().writeUtf8("Hello, World")
    operator.write(0, buffer1, 5)
    assertThat(buffer1.readUtf8()).isEqualTo(", World")
    val buffer2 = Buffer().writeUtf8("icopter!")
    operator.write(3, buffer2, 7)
    assertThat(buffer2.readUtf8()).isEqualTo("!")

    mac.init(SHA1_KEY);
    mac.update("hello".getBytes(UTF_8));
    mac.update("world".getBytes(UTF_8));

    assertEquals(
        HashCode.fromBytes(mac.doFinal()),
        Hashing.hmacSha1(SHA1_KEY)
            .newHasher()
            .putString("hello", UTF_8)
            .putString("world", UTF_8)
            .hash());
  }

  public void testMultipleUpdatesDoFinal() throws Exception {

     *
     * @param searchEngineClient the search engine client to use for deletion
     * @param docList the list of new documents to check against
     * @return the number of old documents that were deleted
     */
    protected long deleteOldDocuments(final SearchEngineClient searchEngineClient, final DocList docList) {
        final FessConfig fessConfig = ComponentUtil.getFessConfig();

        Did you *actually* encounter the need for this feature in a real-world scenario, or is it
        just a feature that seems like a sensible addition to Guava?


        Before new features get added to Guava, we really want to be sure that it's for a use case
        that actually comes up in the real world. We want to hear the real-world use case so the

    /** */
    public int intField;

    /** */
    public String stringField;

    /** */
    public static final int INT_DATA = 987654321;

    /** */
    public static final String STRING_DATA = "Hello World!";

    /**
     * @throws Exception
     */
    @Test
    public void testGet() throws Exception {
        final Field field = getClass().getField("objectField");