User result = chain.load(null);

        assertEquals(loadedUser, result);
        assertEquals(1, chain.loadCalls.size());
        assertNull(chain.loadCalls.get(0));
    }

    // Test load returning null
    public void test_load_returnsNull() {
        TestAuthenticationChain chain = new TestAuthenticationChain();
        chain.loadResult = null;
        User inputUser = createTestUser("inputuser", "Input User");

 * that, in some implementations, data access by column key may have fewer supported operations or
 * worse performance than data access by row key.
 *
 * <p>The methods returning collections or maps always return views of the underlying table.
 * Updating the table can change the contents of those collections, and updating the collections
 * will change the table.
 *

        @Override
        public Object evaluate(String template, Map<String, Object> paramMap) {
            if ("error".equals(template)) {
                // Simulate error by returning null
                return null;
            }
            return template;
        }
    }

    // Test helper class
    private static class TestUser {
        public String name;

  /**
   * In a response, this field's name "no-cache" is misleading. It doesn't prevent us from caching
   * the response; it only means we have to validate the response with the origin server before
   * returning it. We can do this with a conditional GET.
   *
   * In a request, it means do not use a cache to satisfy the request.
   */
  @get:JvmName("noCache") val noCache: Boolean,

            unicodeString.check("");
        });

        // The implementation has a bug - it doesn't handle null properly
        // It throws NullPointerException instead of returning null
        // This is a known issue in the production code
        assertThrows(NullPointerException.class, () -> {
            unicodeString.check(null);
        });
    }

    @Test

        });

        assertEquals("unexpected EOF reading netbios session header", exception.getMessage());
    }

    @Test
    @DisplayName("readPacketType with special stream returning -1 should return -1")
    void testReadPacketTypeSpecialStream() throws IOException {
        // Create a mock stream that returns exactly -1 on first read (special case)

   * given to [connectionUser] who may (for example) assign it to a [RealCall.connection].
   *
   * This confirms the returned connection is healthy before returning it. If this encounters any
   * unhealthy connections in its search, this will clean them up.
   *
   * If [routes] is non-null these are the resolved routes (ie. IP addresses) for the connection.

   *
   * This is typically invoked immediately before bytes are returned to the application. If the
   * response body is empty this is invoked immediately before returning that to the application.
   *
   * If the application closes the response body before attempting a read, this is invoked at the
   * time it is closed.
   *

        HashFunction hashFunction1b = (HashFunction) method.invoke(clazz);

        new EqualsTester().addEqualityGroup(hashFunction1a, hashFunction1b).testEquals();

        // Make sure we're returning not only equal instances, but constants.
        assertSame(hashFunction1a, hashFunction1b);

        assertEquals(hashFunction1a.toString(), hashFunction1b.toString());
      }
    }
  }

   */
  @Deprecated
  @Override
  @InlineMe(replacement = "this.convert(a)")
  public final B apply(A a) {
    /*
     * Given that we declare this method as accepting and returning non-nullable values (because we
     * implement Function<A, B>, as discussed in a class-level comment), it would make some sense to
     * perform runtime null checks on the input and output. (That would also make NullPointerTester