when(s.isClosed()).thenReturn(true);
        assertTrue(transport.isDisconnected());
        assertTrue(transport.isFailed());
    }

    @Test
    @DisplayName("capability query delegates to negotiation state")
    void hasCapability_delegates() throws Exception {
        // Arrange
        SmbNegotiationResponse nego = mock(SmbNegotiationResponse.class);

        }
        return null;
    }

    /**
     *
     * Only call this method while holding a tree handle
     *
     * @param cap
     * @return whether the capability is available
     * @throws SmbException
     */
    public boolean hasCapability(final int cap) throws SmbException {
        try (SmbSessionImpl s = getSession()) {
            if (s != null) {

        assertEquals("test data", new String(buffer));
    }
}

@Test
public void testPersistentHandleSurvivesReboot() throws Exception {
    // This test requires special setup with server reboot capability
    CIFSContext context = getTestContext();
    context.getConfig().setProperty("jcifs.smb.client.usePersistentHandles", "true");
    
    SmbFile file = new SmbFile("smb://server/share/persistent.txt", context);

        javaPluginExtension.registerFeature(name + "Artifacts", featureSpec -> {
            featureSpec.usingSourceSet(sourceSet);
            featureSpec.capability("org.elasticsearch.gradle", project.getName() + "-" + name + "-artifacts", "1.0");
            // This feature is only used internally in the
            // elasticsearch build so we do not need any publication.

    throwing in 5.0.0, we inadvertently removed the ability for callers to peek the trailers
    (by catching the `IllegalStateException` if they weren't available). This new API restores that
    capability.

 *  Fix: Don't crash on `trailers()` if the response doesn't have a body. We broke [Retrofit] users
    who read the trailers on the `raw()` OkHttp response, after its body was decoded.


## Version 5.0.0

        @Override
        protected void commandStyle(LineReader reader, AttributedStringBuilder sb, boolean enable) {
            if (enable) {
                if (reader.getTerminal().getNumericCapability(InfoCmp.Capability.max_colors) >= 256) {
                    sb.style(AttributedStyle.DEFAULT.bold().foreground(69));
                } else {
                    sb.style(AttributedStyle.DEFAULT.foreground(AttributedStyle.CYAN));

# This is the same as the official TensorFlow builds.
# See https://developer.nvidia.com/cuda-gpus#compute
# `compute_XY` enables PTX embedding in addition to SASS. PTX
# is forward compatible beyond the current compute capability major
# release while SASS is only forward compatible inside the current
# major release. Example: sm_80 kernels can run on sm_89 GPUs but
# not on sm_90 GPUs. compute_80 kernels though can also run on sm_90 GPUs.

### SIG Scalability

SIG Scalability has mostly focused on stability and deflaking our tests, investing into framework for writing scalability tests (ClusterLoader v2) with a goal to migrate all tests to it by the end of 2018 and on the work towards extending definition of Kubernetes scalability by providing more/better user-friendly SLIs/SLOs.

### SIG Scheduling

- The certificate signer no longer accepts ca.key passwords via the `CFSSL_CA_PK_PASSWORD` environment variable. This capability was not prompted by user request, never advertised, and recommended against in the security audit. ([#84677](https://github.com/kubernetes/kubernetes/pull/84677), [@mikedanese](https://github.com/mikedanese))

### SIG Scalability

[SIG Scalability][] is responsible for scalability testing, measuring and
improving system performance, and answering questions related to scalability.

For the 1.8 release, SIG Scalability focused on automating large cluster
scalability testing in a continuous integration (CI) environment. The SIG
defined a concrete process for scalability testing, created