// the null value might be out of bounds, so we can't always construct a subset with nulls
      features.add(CollectionFeature.ALLOWS_NULL_QUERIES);
      // but add null might still be supported if it happens to be within range of the subset
      suppressing.add(CollectionAddTester.getAddNullUnsupportedMethod());
      suppressing.add(CollectionAddAllTester.getAddAllNullUnsupportedMethod());
    }

			"dir/object1",
			[]string{"object0"},
		},
		// Test 3: remove an object inside a directory and checks if it is deleted
		// but other sibling object in the same directory still exists
		{
			"bucket3",
			[]objectUpload{{"dir/object1", "content"}, {"dir/object2", "content"}},
			"dir/object1",
			[]string{"dir/object2"},
		},

 * of {@link java.util.Formatter} specifiers. However, note that if the number of arguments does not
 * match the number of occurrences of {@code "%s"} in the format string, {@code Verify} will still
 * behave as expected, and will still include all argument values in the error message; the message
 * will simply not be formatted exactly as intended.
 *
 * <h3>More information</h3>
 *

            // Act
            SmbNamedPipe pipe = new SmbNamedPipe("smb://server/IPC$/foo", flags, ctx());

            // Assert: observable properties still correct
            assertEquals(flags, pipe.getPipeType());
            assertEquals(SmbConstants.TYPE_NAMED_PIPE, pipe.getType());
        }
    }

    @Test

            smbtStatic.close();
        }
    }

    @Test
    void transportLazyInitialisation() {
        SmbSession session = new SmbSession(addr, 445, inet, 0, auth);
        // transport should still be null until first use
        assertNull(session.transport, "transport not created yet");
        SmbTransport tr = session.transport();
        assertNotNull(tr, "transport should now exist");

   * next} field is lazily initialized. The type of that field would be {@code @Nullable T}, and the
   * code would be responsible for populating a "real" {@code T} (which might still be the value
   * {@code null}!) before returning it to callers. Depending on how the code is structured, a
   * nullness analysis might not understand that the field has been populated. To avoid that problem

   * next} field is lazily initialized. The type of that field would be {@code @Nullable T}, and the
   * code would be responsible for populating a "real" {@code T} (which might still be the value
   * {@code null}!) before returning it to callers. Depending on how the code is structured, a
   * nullness analysis might not understand that the field has been populated. To avoid that problem

```

////

## Recap { #recap }

Apart from all the fancy words used here, the **Dependency Injection** system is quite simple.

Just functions that look the same as the *path operation functions*.

But still, it is very powerful, and allows you to declare arbitrarily deeply nested dependency "graphs" (trees).

/// tip

All this might not seem as useful with these simple examples.

        // Then
        assertNotNull(signingKey, "Should handle empty session key");
        assertEquals(16, signingKey.length, "Should still produce 16-byte key");
    }

    @Test
    @DisplayName("Should handle null preauth integrity for SMB 3.0.0")
    void testDeriveKeys_NullPreauthForSMB300() {
        // Given

     */
    SmbPipeResource getPipe(String url, int pipeType) throws CIFSException;

    /**
     * Close all connections and release resources associated with this context
     *
     * @return whether any connection was still in use
     * @throws CIFSException if an error occurs during cleanup
     */
    boolean close() throws CIFSException;

    /**
     * Get the configuration object for this context
     *