* that behavior is undefined when the backing map is modified through another API. (It even
       * permits us to throw IllegalStateException. Maybe we should have done that, but we probably
       * shouldn't change now for fear of breaking people.)
       */
      return (lastKnownIndex == -1) ? unsafeNull() : value(lastKnownIndex);
    }

    @Override
    @ParametricNullness

    assertThat(c.toString()).isEqualTo("Ordering.explicit([0])");
  }

  public void testExplicitMax_b297601553() {
    Ordering<Integer> c = Ordering.explicit(1, 2, 3);

    // TODO(b/297601553): this should probably throw CCE since 0 isn't explicitly listed
    assertEquals(0, (int) c.max(asList(0)));
    IncomparableValueException expected =
        assertThrows(IncomparableValueException.class, () -> c.max(asList(0, 1)));

    assertThat(c.toString()).isEqualTo("Ordering.explicit([0])");
  }

  public void testExplicitMax_b297601553() {
    Ordering<Integer> c = Ordering.explicit(1, 2, 3);

    // TODO(b/297601553): this should probably throw an CCE since 0 isn't explicitly listed
    assertEquals(0, (int) c.max(asList(0)));
    IncomparableValueException expected =
        assertThrows(IncomparableValueException.class, () -> c.max(asList(0, 1)));

      @Override
      public OutputStream openStream() throws IOException {
        return encodingStream(encodedSink.openStream());
      }
    };
  }

  // TODO(lowasser): document the extent of leniency, probably after adding ignore(CharMatcher)

  private static byte[] extract(byte[] result, int length) {
    if (length == result.length) {
      return result;
    }
    byte[] trunc = new byte[length];

### DELETE operation in REST API

    /*
     * Even though it's weird to pass a defaultValue that is null, some callers do so. Those who
     * pass a literal "null" should probably just use `get`, but I would expect other callers to
     * pass an expression that *might* be null. This could happen with:
     *
     * - a `getFooOrDefault(@Nullable Foo defaultValue)` method that returns

  //
  // This idea has come up from time to time, and I think one of my
  // earlier versions of Monitor even did something like this. I ended
  // up strongly favoring the current interface.
  //
  // I probably can't remember all the reasons (it's possible you
  // could find them in the code review archives), but here are a few:
  //
  // 1. What about leaving/unlocking? Are you going to do

   */
  protected TypeToken() {
    this.runtimeType = capture();
    checkState(
        !(runtimeType instanceof TypeVariable),
        "Cannot construct a TypeToken for a type variable.\n"
            + "You probably meant to call new TypeToken<%s>(getClass()) "
            + "that can resolve the type variable for you.\n"
            + "If you do need to create a TypeToken of a type variable, "

- The `kube-proxy` command-line documentation was updated to clarify that
  `--bind-address` does not actually have anything to do with binding to an
  address, and you probably don't actually want to be using it. ([#120274](https://github.com/kubernetes/kubernetes/pull/120274), [@danwinship](https://github.com/danwinship))

- Fixed a data race in k8s.io/apiserver/pkg/cel/openapi/resolver with (probably) no real-world impact. ([#136802](https://github.com/kubernetes/kubernetes/pull/136802), [@pohly](https://github.com/pohly)) [SIG API Machinery, Node and Testing]
- Fixed kubectl logs -f to wait for containers to start instead of failing