*
     * @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();

        String result = purgeLogJob.execute();

        // Assert all services were called
        assertTrue(deleteCrawlingInfoCalled[0]);
        assertTrue(deleteSearchLogCalled[0]);
        assertTrue(deleteJobLogCalled[0]);
        assertTrue(deleteUserInfoCalled[0]);
        assertTrue(updateJobLogStatusCalled[0]);

        // Assert correct parameters were passed - verify that time passed is greater than 0

        // Perform the renewal
        boolean renewed = wrapper.renewCredentials("locationHint", null);

        // Verify that renew() was called and credentials were updated
        assertTrue(renewed, "renewCredentials should return true when renewable credentials are renewed");

with Java.

We spent a lot of time and energy on retaining strict compatibility with OkHttp 3.x. We’re even
keeping the package name the same: `okhttp3`!

There are three kinds of compatibility we’re tracking:

 * **Binary compatibility** is the ability to compile a program against OkHttp 3.x, and then to run
   it against OkHttp 4.x. We’re using the excellent [japicmp][japicmp] library via its

 * the keys in the order they were first added to the multimap. Similarly, {@code get}, {@code
 * removeAll}, and {@code replaceValues} return collections that iterate through the values in the
 * order they were added. The collections generated by {@code entries} and {@code values} iterate
 * across the key-value mappings in the order they were added to the multimap.
 *

 * the keys in the order they were first added to the multimap. Similarly, {@code get}, {@code
 * removeAll}, and {@code replaceValues} return collections that iterate through the values in the
 * order they were added. The collections generated by {@code entries} and {@code values} iterate
 * across the key-value mappings in the order they were added to the multimap.
 *

	}

	rows, err := gorm.G[User](DB).Where("id = ?", user.ID).Set(assocOp).Update(ctx)
	if err != nil {
		t.Fatalf("Set Update with many-to-many association failed: %v", err)
	}
	// Only association operations were executed; no row update is expected
	if rows != 0 {
		t.Fatalf("expected 0 rows affected for association-only update, got %d", rows)
	}

	// Verify the languages were associated using real database query

        byte[] data2 = "World".getBytes();

        // When
        outputStream.write(data1);
        outputStream.write(data2);

        // Then - verify two write requests were sent
        verify(mockTreeHandle, times(2)).send(any(Smb2WriteRequest.class), any());
    }

    @Test
    void testConstructorWithSmbFileOnly() throws IOException, CIFSException {
        // Given

 * the order they were first added to the multimap. Similarly, {@link #get}, {@link #removeAll}, and
 * {@link #replaceValues} return collections that iterate through the values in the order they were
 * added. The collections generated by {@link #entries()}, {@link #keys()}, and {@link #values}
 * iterate across the key-value mappings in the order they were added to the multimap.
 *

## Version 4.5.0

_2020-04-06_

**This release fixes a severe bug where OkHttp incorrectly detected and recovered from unhealthy
connections.** Stale or canceled connections were incorrectly attempted when they shouldn't have
been, leading to rare cases of infinite retries. Please upgrade to this release!

 *  Fix: don't return stale DNS entries in `DnsOverHttps`. We were caching DNS results indefinitely