public ChannelInfo selectChannel(CommonServerMessageBlock message) {
        return loadBalancer.selectChannel(message);
    }

    /**
     * Handle channel failure
     *
     * @param channel failed channel
     * @param error error that caused failure
     */
    public void handleChannelFailure(ChannelInfo channel, Exception error) {
        failover.handleFailure(channel, error);
    }

    /**

        assertThrows(SmbException.class, () -> tree.treeConnect(null, null));
        // After failure, state should be reset to disconnected
        assertEquals(0, tree.connectionState);
    }

    @Test
    void testSend() throws SmbException {
        SmbTree tree = new SmbTree(session, "testShare", "A:");

 *     .build();
 * client.newCall(request).execute();
 * ```
 *
 * As expected, this fails with a certificate pinning exception:
 *
 * ```java
 * javax.net.ssl.SSLPeerUnverifiedException: Certificate pinning failure!
 * Peer certificate chain:
 *     sha256/afwiKY3RxoMmLkuRW1l7QsPZTJPwDS2pdDROQjXw8ig=: CN=publicobject.com, OU=PositiveSSL
 *     sha256/klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY=: CN=COMODO RSA Secure Server CA

            } else if (!artifact.getFile().exists()) {
                String error = updateCheckManager.getError(artifact, repository);
                if (error != null) {
                    throw new TransferFailedException("Failure to resolve " + remotePath + " from "
                            + repository.getUrl()
                            + " was cached in the local repository. "

                 * junk. We need to bump up the wordCount here so that this method returns
                 * the correct number of bytes for signing purposes. Otherwise we get a
                 * signing verification failure.
                 */
                if (command == SMB_COM_NT_CREATE_ANDX && ((SmbComNTCreateAndXResponse) this).isExtended) {
                    wordCount += 8;
                }
            }

        // Act & Assert
        assertThrows(NullPointerException.class, () -> handler.openConnection(null), "Null URL should throw NPE");
        verify(mockCtx, never()).getConfig(); // no interaction expected on failure before construction
    }

    @Test
    @DisplayName("openConnection uses SingletonContext when no context provided")
    void testOpenConnection_UsesSingletonContext() throws Exception {
        // Arrange

# Application Exception
# ---------------------
# /- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = Falha no login.
errors.app.illegal.transition = Transição ilegal. Por favor, tente novamente.
errors.app.db.already.deleted = Pode ter sido excluído por outro processo. Por favor, tente novamente.

      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

     * and cleanup operations.
     *
     * @param options parsed command-line options containing crawling configuration
     * @return exit code (Constants.EXIT_OK for success, Constants.EXIT_FAIL for failure)
     */
    private static int process(final Options options) {
        final Crawler crawler = ComponentUtil.getComponent(Crawler.class);

        if (StringUtil.isBlank(options.sessionId)) {

server in a given timeframe for whatever reasons (networking issue, machine
failure, etc.). Normally when kube-up script will encounter even one NotReady
node it will fail, even though the cluster most likely will be working. We
added an environmental variable to kube-up ALLOWED\_NOTREADY\_NODES that
defines the number of nodes that if not Ready in time won’t cause kube-up
failure.
  * “kubectl rolling-update” only supports Replication Controllers (it doesn’t