* Fixes an issue where the resourceVersion of an object in a DELETE watch event was not the resourceVersion of the delete itself, but of the last update to the object. This could disrupt the ability of clients clients to re-establish watches properly. ([#58547](https://github.com/kubernetes/kubernetes/pull/58547), [@liggitt](https://github.com/liggitt))

        channel1 = new ChannelInfo("channel1", mockTransport1, local, remote1);
        channel1.setState(ChannelState.ESTABLISHED);

        channel2 = new ChannelInfo("channel2", mockTransport2, local, remote2);
        channel2.setState(ChannelState.ESTABLISHED);
    }

    @Test
    void testSingleChannelSelection() {

        channel.setState(ChannelState.ESTABLISHED);

        // Verify channel properties
        assertEquals("test-channel", channel.getChannelId());
        assertEquals(mockTransport, channel.getTransport());
        assertEquals(localNic, channel.getLocalInterface());
        assertEquals(remoteNic, channel.getRemoteInterface());
        assertEquals(ChannelState.ESTABLISHED, channel.getState());

        }
        ret.append("]");
        return ret.toString();
    }

    /**
     * Checks whether the security context is established.
     * @return true if the context is established, false otherwise
     */
    public boolean isEstablished() {
        return isEstablished;
    }

    /**
     * Gets the server's NTLM challenge bytes.

     * @throws CIFSException if an error occurs retrieving the signing key
     */
    byte[] getSigningKey() throws CIFSException;

    /**
     * Checks whether the security context is established.
     * @return whether the context is established
     */
    boolean isEstablished();

    /**
     * Initializes the security context with the given token.
     * @param token the input token bytes

- The project / component that contains the reported vulnerability.
- A description of the vulnerability. In particular, the type of the
   reported vulnerability and how it might be exploited. Alternatively,
   a well-established vulnerability identifier, e.g. CVE number, can be
   used instead.

Based on the description mentioned above, a MinIO engineer or security team
member investigates:

- Whether the reported vulnerability exists.

     *
     * @return whether the share is in DFS
     */
    boolean isShareDfs();

    /**
     * Indicates whether the tree connection has been successfully established and has a valid tree ID.
     *
     * @return whether the tree id is a valid one
     */
    boolean isValidTid();

import jcifs.internal.smb1.AndXServerMessageBlock;
import jcifs.internal.smb1.ServerMessageBlock;

/**
 * SMB1 Logoff AndX request message.
 *
 * This command is used to terminate a user session that was
 * previously established with a Session Setup AndX command.
 */
public class SmbComLogoffAndX extends AndXServerMessageBlock {

    /**
     * Creates a new SMB1 logoff request to end a user session.
     *

import org.jspecify.annotations.Nullable;

/**
 * To be implemented by test generators of things that can contain elements. Such things include
 * both {@link Collection} and {@link Map}; since there isn't an established collective noun that
 * encompasses both of these, 'container' is used.
 *
 * @author George van den Driessche
 */
@GwtCompatible
@NullMarked
public interface TestContainerGenerator<T, E extends @Nullable Object> {

    /**
     * Connect to a remote RDMA endpoint
     *
     * @param hostname remote hostname or IP address
     * @param port remote port number
     * @return established RDMA connection
     * @throws IOException if connection fails
     */
    RdmaConnection connect(String hostname, int port) throws IOException;

    /**
     * Register memory region for RDMA operations
     *