}
            } catch (final SmbException e) {
                if (e.getNtStatus() == NtStatus.NT_STATUS_INVALID_PARAMETER) {
                    // Silently ignore invalid parameter errors - these may occur with certain server configurations
                    if (log.isDebugEnabled()) {
                        log.debug("Invalid parameter error.", e);
                    }
                    return;
                }

  <mime-type type="text/vnd.abc"/>
  <mime-type type="text/vnd.curl">
    <glob pattern="*.curl"/>
  </mime-type>
  <mime-type type="text/vnd.curl.dcurl">
    <glob pattern="*.dcurl"/>
  </mime-type>
  <mime-type type="text/vnd.curl.scurl">
    <glob pattern="*.scurl"/>
  </mime-type>
  <mime-type type="text/vnd.curl.mcurl">
    <glob pattern="*.mcurl"/>
  </mime-type>

 * <p>This pattern ensures the following:
 *
 * <ul>
 *   <li>Each {@code Closeable} resource that is successfully registered will be closed later.
 *   <li>If a {@code Throwable} is thrown in the try block, no exceptions that occur when attempting
 *       to close resources will be thrown from the finally block. The throwable from the try block
 *       will be thrown.

 * specified the JVM flag {@code -XX:+DisableExplicitGC}. But in practice, it works very well for
 * ordinary tests.
 *
 * <p>Failure of the expected event to occur within an implementation-defined "reasonable" time
 * period or an interrupt while waiting for the expected event will result in a {@link
 * RuntimeException}.
 *
 * <p>Here's an example that tests a {@code finalize} method:

     *
     * @param result the list of search results
     * @param consumer the BiConsumer to process entry DN and role name
     * @throws NamingException if LDAP naming exception occurs
     */
    protected void processSearchRoles(final List<SearchResult> result, final BiConsumer<String, String> consumer) throws NamingException {
        processSearchRoles(result, entryDn -> {

requires a setting in the replication configuration called [replica modification sync](https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-replication-adds-support-two-way-replication/).

For active-active replication, automatic failover occurs on `GET/HEAD` operations if object or object version requested qualifies for replication and is missing on one site, but present on the other. This allows the applications to take full advantage of two-way replication even before the two sites get...

	public final fun tag (Ljava/lang/Class;)Ljava/lang/Object;
	public final fun tag (Lkotlin/reflect/KClass;)Ljava/lang/Object;
	public final fun toCurl ()Ljava/lang/String;
	public final fun toCurl (Z)Ljava/lang/String;
	public static synthetic fun toCurl$default (Lokhttp3/Request;ZILjava/lang/Object;)Ljava/lang/String;
	public fun toString ()Ljava/lang/String;
	public final fun url ()Lokhttp3/HttpUrl;
}

			expectedExpiry := ExpectedExpiryTime(obj.SuccessorModTime, int(rule.NoncurrentVersionExpiration.NoncurrentDays))
			if now.IsZero() || now.After(expectedExpiry) {
				oldEnough = true
			}
			// > For the deletion to occur, both the <NoncurrentDays> and the <NewerNoncurrentVersions> values must be exceeded.
			// ref: https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#intro-lifecycle-rules-actions

        }

        // We are forcing the use of the plugin realm for all lookups that might occur during
        // the lifecycle that is part of the lookup. Here we are specifically trying to keep
        // lookups that occur in contextualize calls in line with the right realm.
        ClassRealm oldLookupRealm = container.setLookupRealm(pluginRealm);

                            ex = new SmbAuthException("Login failed", se);
                        }
                        /*
                         * Apparently once a successful NTLMSSP login occurs, the
                         * server will return "Access denied" even if a logoff is
                         * sent. Unfortunately calling disconnect() doesn't always