changes are numerous but most are cosmetic. Applications should be able to
upgrade from the 2.x API to the 3.x API mechanically and without risk.

Because the release includes breaking API changes, we're changing the project's
package name from `com.squareup.okhttp` to `okhttp3`. This should make it
possible for large applications to migrate incrementally. The Maven group ID

        long expectedValue = 123456789012345L;
        NdrHyper ndrHyper = new NdrHyper(expectedValue);
        assertEquals(expectedValue, ndrHyper.value, "Constructor should set the correct value.");
    }

    @Test
    void testEncode() throws NdrException {
        // Test the encode method
        long testValue = 987654321098765L;
        NdrHyper ndrHyper = new NdrHyper(testValue);

  @CollectionFeature.Require(SUPPORTS_ADD)
  @CollectionSize.Require(absent = ZERO)
  public void testAddAll_supportedAllPresent() {
    assertTrue(
        "addAll(allPresent) should return true", getList().addAll(MinimalCollection.of(e0())));
    expectAdded(e0());
  }

  @CollectionFeature.Require(absent = SUPPORTS_ADD)
  @CollectionSize.Require(absent = ZERO)

   *
   * 2. `other[size] = null` is unsound. We could "fix" this by requiring callers to pass in an
   * array with a nullable element type. But probably they usually want an array with a non-nullable
   * type. That said, we could *accept* a `@Nullable T[]` (which, given that we treat arrays as
   * covariant, would still permit a plain `T[]`) and return a plain `T[]`. But of course that would

          <description>
            Whether Maven should attempt to interact with the user for input.
          </description>
          <type>boolean</type>
          <defaultValue>true</defaultValue>
        </field>
        <field>
          <name>usePluginRegistry</name>
          <version>1.0.0+</version>
          <description>
            Whether Maven should use the {@code plugin-registry.xml} file to manage plugin versions.

        // Test List interface (should use get(0) for performance)
        List<BsUser> list = Arrays.asList(entity1, entity2);
        RenderDataUtil.register(data, "list", list);

        Object result = data.getDataMap().get("list");
        assertNotNull(result);
        assertTrue(result instanceof List);

        // Test Set interface (should use iterator().next())

        scoreUpdater.addScoreBooster(booster3);

        // Clear execution order before test
        PriorityTrackingBooster.clearExecutionOrder();

        scoreUpdater.execute();

        // Boosters should be executed in priority order (3, 2, 1)
        List<Integer> executionOrder = PriorityTrackingBooster.getExecutionOrder();
        assertEquals(3, executionOrder.size());

  }

  private void expectReturnsTrue(Target target) {
    String message = Platform.format("retainAll(%s) should return true", target);
    assertTrue(message, collection.retainAll(target.toRetain));
  }

  private void expectReturnsFalse(Target target) {
    String message = Platform.format("retainAll(%s) should return false", target);
    assertFalse(message, collection.retainAll(target.toRetain));
  }

        boolBuilder.add(new TermQuery(new Term("field1", "value1")), BooleanClause.Occur.MUST);
        boolBuilder.add(new TermQuery(new Term("field2", "value2")), BooleanClause.Occur.SHOULD);
        BooleanQuery boolQuery = boolBuilder.build();
        BoostQuery boostQuery = new BoostQuery(boolQuery, 2.0f);

        QueryContext context = new QueryContext("test", false);

   * to stop requests. You could poll for lifecycle changes in a work loop:
   *
   * <pre>
   *   public void run() {
   *     while ({@link #isRunning()}) {
   *       // perform a unit of work
   *     }
   *   }
   * </pre>
   *
   * <p>...or you could respond to stop requests by implementing {@link #triggerShutdown()}, which
   * should cause {@link #run()} to return.
   */