4.2.2.
 *  Fix: Drop partial support for HTTP/1.0. Previously OkHttp would send
    `HTTP/1.0` on connections after seeing a response with `HTTP/1.0`. The fixed
    behavior is consistent with Firefox and Chrome.
 *  Fix: Allow a body in `OPTIONS` requests.
 *  Fix: Don't percent-encode non-ASCII characters in URL fragments.
 *  Fix: Handle null fragments.

		tops = tops[:0]
		var topSig xlMetaV2VersionHeader
		consistent := true // Are all signatures consistent (shortcut)
		for _, vers := range versions {
			if len(vers) == 0 {
				consistent = false
				continue
			}
			ver := vers[0]
			if len(tops) == 0 {
				consistent = true
				topSig = ver.header
			} else {
				consistent = consistent && ver.header == topSig
			}
			tops = append(tops, vers[0])

            // Then
            assertEquals(443, httpsPort);
            assertNotEquals(jcifs.smb1.http.Handler.DEFAULT_HTTP_PORT, httpsPort);
        }

        @Test
        @DisplayName("Should return consistent port value")
        void testPortConsistency() {
            // When
            int port1 = handler.getDefaultPort();
            int port2 = handler.getDefaultPort();
            int port3 = handler.getDefaultPort();

        URL url2 = new URL(null, "smb://host2/share2", handler);

        // Both should use the same handler instance
        assertNotNull(url1);
        assertNotNull(url2);

        // Protocol should be consistent
        assertEquals(url1.getProtocol(), url2.getProtocol());
        assertEquals("smb", url1.getProtocol());
    }

   * Inet4Address} objects, not {@link Inet6Address}. This is consistent with the behavior of {@link
   * InetAddress}.
   *
   * <p>This method accepts non-ASCII digits, for example {@code "１９２.１６８.０.１"} (those are fullwidth
   * characters). That is consistent with {@link InetAddress}, but not with various RFCs. If you
   * want to accept ASCII digits only, you can use something like {@code

                    // Note that Firefox is fine with a sort function returning any positive or negative number, but Chrome
                    // requires 1 or -1 specifically and ignores higher or lower values.  This sort ought to remain consistent
                    // with the sort used by AbstractAcceptedApiChangesMaintenanceTask.
                    result.acceptedApiChanges.sort((a, b) => {

/**
 * Handles basic types that always use the same tag. This supports optional types and may set a type
 * hint for further adapters to process.
 *
 * Types like ANY and CHOICE that don't have a consistent tag cannot use this.
 */
internal data class BasicDerAdapter<T>(
  private val name: String,
  /** The tag class this adapter expects, or -1 to match any tag class. */
  val tagClass: Int,

 * equality for both keys and values. This may not be the desired behavior for map implementations
 * that use non-standard notions of key equality, such as the entry of a {@code SortedMap} whose
 * comparator is not consistent with {@code equals}.
 *
 * <p>The {@code standard} methods are not guaranteed to be thread-safe, even when all of the
 * methods that they depend on are thread-safe.
 *
 * @author Mike Bostock
 * @author Louis Wasserman

        assertTrue(toStringResult.contains(message));
    }

    @Test
    public void test_getMessage_consistency() {
        // Test that getMessage returns the same value consistently
        String message = "Consistent message";
        UnsupportedSearchException exception = new UnsupportedSearchException(message);

        String firstCall = exception.getMessage();
        String secondCall = exception.getMessage();

			t.Errorf("Test case %d, expect to pass but failed. Wanted modTime: %s, got modTime: %s\n", i+1, testCase.time, ctime)
		}
	}
}

// TestListOnlineDisks - checks if listOnlineDisks and outDatedDisks
// are consistent with each other.
func TestListOnlineDisks(t *testing.T) {
	if runtime.GOOS == globalWindowsOSName {
		t.Skip()
	}

	ctx, cancel := context.WithCancel(t.Context())
	defer cancel()