// Due to normalization removing duplicate backslashes, true UNC validation doesn't work
        // These tests validate current behavior where problematic paths are caught by other checks

        // Test invalid server name with dots - caught by directory traversal check
        assertThrows(SmbException.class, () -> {
            validator.validatePath("\\\\..\\share");
        });

            }
        }
        return target;
    }

    /**
     * Updates a document with additional metadata and enhancements.
     * Adds click counts, favorite counts, document boosting, and generates document ID.
     * Also applies language-specific updates through the language helper.
     *
     * @param map the document data map to update with additional metadata
     */

     * implement Function<A, B>, as discussed in a class-level comment), it would make some sense to
     * perform runtime null checks on the input and output. (That would also make NullPointerTester
     * happy!) However, since we didn't do that for many years, we're not about to start now.
     * (Runtime checks could be particularly bad for users of LegacyConverter.)
     *

            if (isSuitable(methodDesc.getParameterTypes(), args, true)) {
                return methodDesc;
            }
        }
        return null;
    }

    /**
     * Checks whether the arguments are suitable for the parameter types.
     *
     * @param paramTypes
     *            array of parameter types
     * @param args
     *            array of arguments

    distinctValues.replaceValues(type, ImmutableList.of(value1, value2));
    setDefault(type, value1);
    return this;
  }

  /**
   * Tests that {@code cls} properly checks null on all constructor and method parameters that
   * aren't annotated nullable (according to the rules of {@link NullPointerTester}). In details:
   *
   * <ul>

            errorPoms.addAll(pomMap.keySet());
        }

        return new UpgradeResult(processedPoms, modifiedPoms, errorPoms);
    }

    /**
     * Upgrades plugins in the document.
     * Checks both build/plugins and build/pluginManagement/plugins sections.
     * Only processes plugins explicitly defined in the current POM document.
     */

 * explained</a> in the Guava User Guide for more advice. Notably, {@link Verify} offers assertions
 * similar to those in this class for non-precondition checks.
 *
 * <h3>{@code java.util.Objects.requireNonNull()}</h3>
 *
 * <p>Projects which use {@code com.google.common} should generally avoid the use of {@link

    }

    synchronized void close() throws IOException {
      out.close();
    }

    synchronized void flush() throws IOException {
      out.flush();
    }

    /**
     * Checks if writing {@code len} bytes would go over threshold, and switches to file buffering
     * if so.
     */
    @GuardedBy("this")
    void update(int len) throws IOException {

But there could be cases where you want to be able to set parameters on the dependency, without having to declare many different functions or classes.

Let's imagine that we want to have a dependency that checks if the query parameter `q` contains some fixed content.

But we want to be able to parameterize that fixed content.

## A "callable" instance { #a-callable-instance }

    /** Scroll timeout for update operations */
    protected String scrollForUpdate = "1m";

    /** Maximum retry attempts for configuration synchronization status checks */
    protected int maxConfigSyncStatusRetry = 10;

    /** Maximum retry attempts for search engine status checks */
    protected int maxEsStatusRetry = 60;

    /** Name of the search engine cluster */
    protected String clusterName = "fesen";