} catch (AssertionFailedError expected) {
      for (String message : expectedMessages) {
        assertThat(expected).hasMessageThat().contains(message);
      }
      return;
    }
    fail("expected failure not reported");
  }

  private static class ForwardingRunnable implements Runnable {

    private final Runnable runnable;

    ForwardingRunnable(Runnable runnable) {
      this.runnable = runnable;

                 * 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;
                }
            }

            logger
                .get()
                .log(
                    Level.WARNING,
                    "Error while attempting to shut down the service after failure.",
                    ignored);
          }
          notifyFailed(t);
          // requireNonNull is safe now, just as it was above.
          requireNonNull(runningTask).cancel(false); // prevent future invocations.

     * 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

                                logger.warn("Authentication Failure: {} - Reason: {}", errors.stream().collect(Collectors.joining(", ")),
                                        auth.getLastErrorReason());
                            } else {
                                logger.warn("Authentication Failure: {}", errors.stream().collect(Collectors.joining(", ")));
                            }

    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);
    }

    /**

        BAD_REQUEST(1),
        /** System error status indicating server error. */
        SYSTEM_ERROR(2),
        /** Unauthorized status indicating authentication failure. */
        UNAUTHORIZED(3),
        /** General failure status. */
        FAILED(9);

        private final int id;

        Status(final int id) {
            this.id = id;
        }

        /**

    }

    /**
     * Deletes a label type setting by ID.
     *
     * @param id the ID of the label type setting to delete
     * @return JSON response indicating success or failure
     */
    // DELETE /api/admin/labeltype/setting/{id}
    @Execute
    public JsonResponse<ApiResult> delete$setting(final String id) {
        labelTypeService.getLabelType(id).ifPresent(entity -> {

        throw new NullPointerException("at index " + i);
      }
      list.add(element);
    }
    equalityGroups.add(list);
    return this;
  }

  /** Run tests on equals method, throwing a failure on an invalid test */
  @CanIgnoreReturnValue
  public EqualsTester testEquals() {
    RelationshipTester<Object> delegate =
        new RelationshipTester<>(