* When annotating existing internal code, use `org.jetbrains.annotations.Contract`, e.g. `@Contract(null -> null; !null -> !null)`.
      When doing so, still annotate nullable parameters and the return type as `@Nullable`.
  * Do not use `@Contract` for public APIs.
  * For polynull public APIs, the solution has to be decided on a case-by-case basis.

    latch.awaitSuccessfully(LONG_DELAY_MS);
    assertInterrupted();
  }

  public void testAwaitTimeoutMultiInterruptExpired() {
    /*
     * We don't "need" to schedule a countDown() call at all here, but by doing
     * so, we come the closest we can to testing that the wait time is
     * appropriately decreased on each progressive await() call.
     */
    TimedLatch latch = new TimedLatch(/* countdownInMillis= */ LONG_DELAY_MS);

     *
     * @param dir the directory containing the file
     * @param name the name of the file
     * @return whether the given filename should be included
     * @throws SmbException if an SMB error occurs during evaluation
     */
    boolean accept(SmbFile dir, String name) throws SmbException;

// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package replication

import (
	"fmt"
)

// Error is the generic type for any error happening during tag
// parsing.
type Error struct {
	err error
}

// Errorf - formats according to a format specifier and returns
// the string as a value that satisfies error of type tagging.Error

to be initialized but the results are assumed uninitialized.
If the results will hold live pointers during a call instruction,
the function should start by zeroing the results and then
executing the pseudo-instruction <code>GO_RESULTS_INITIALIZED</code>.
This instruction records that the results are now initialized
and should be scanned during stack movement and garbage collection.
It is typically easier to arrange that assembly functions do not

 * that it is not "API-frozen."
 *
 * <p>It is generally safe for <i>applications</i> to depend on beta APIs, at the cost of some extra
 * work during upgrades. However it is generally inadvisable for <i>libraries</i> (which get
 * included on users' CLASSPATHs, outside the library developers' control) to do so.
 *
 * @author Kevin Bourrillion
 */

 * that it is not "API-frozen."
 *
 * <p>It is generally safe for <i>applications</i> to depend on beta APIs, at the cost of some extra
 * work during upgrades. However it is generally inadvisable for <i>libraries</i> (which get
 * included on users' CLASSPATHs, outside the library developers' control) to do so.
 *
 * @author Kevin Bourrillion
 */

    /**
     * Connects and performs logon to the tree using the specified context
     * @param tf the CIFS context to use for connection
     * @throws SmbException if an SMB error occurs during connection
     */
    @Deprecated
    void connectLogon(CIFSContext tf) throws SmbException;

    /**
     * Sends an SMB request and returns the response
     * @param <T> the response type

 *
 * <p>Each result is linked to its originating {@link Request}, allowing for:
 * <ul>
 *   <li>Traceability between requests and their outcomes</li>
 *   <li>Access to the session context used during processing</li>
 *   <li>Correlation of results with their initiating parameters</li>
 * </ul>
 *
 * @param <REQ> the type of Request that produced this result, ensuring type-safe

        void nullDelegate_throwsNPE() throws Exception {
            SmbFile parent = newParent();
            assertThrows(NullPointerException.class, () -> new ShareEnumIterator(parent, null, null));
        }

        @Test
        @DisplayName("Null parent with non-empty iterator causes NullPointerException during adapt")
        void nullParent_throwsNPE() {