*
     * @return the clientGuid
     */
    public byte[] getClientGuid() {
        return this.clientGuid;
    }

    /**
     * Gets the negotiate contexts for SMB 3.1.1 negotiation.
     *
     * @return the negotiateContexts
     */
    public NegotiateContextRequest[] getNegotiateContexts() {
        return this.negotiateContexts;
    }

    /**

  TFE_CancelCallback callback2;
  bool callback2_invoked = false;
  callback2.context = &callback2_invoked;
  callback2.callback = [](void* context) {
    *reinterpret_cast<bool*>(context) = true;
  };
  TFE_CancellationToken token2 = TFE_CancellationManagerGetToken(c_mgr);
  EXPECT_TRUE(TFE_CancellationManagerRegisterCallback(c_mgr, token2, &callback2,

        assertFalse(Arrays.equals(derived1, derived2), "Different labels should produce different keys");
        assertFalse(Arrays.equals(derived1, derived3), "Different contexts should produce different keys");
    }

    @Test
    public void testStoreNullKey() {
        assertThrows(IllegalArgumentException.class, () -> keyManager.storeSessionKey("session", null, "AES"));
    }

should have a convention set, so (1) can be treated as a rare case where a value must be provided by a user.

Best practice is to set conventions in a plugin (2). This keeps the underlying object "dumb", so it can be reused in multiple contexts and doesn't contain any special information about how conventions are calculated or what they could be.  In the wild, we've seen some objects set conventions in the object's constructor (3), but this can lead to unexpected assumptions or coupling...

            "maven.versionRangeResolver.natureOverride";

    /**
     * Comma-separated list of XML contexts/fields to intern during POM parsing for memory optimization.
     * When not specified, a default set of commonly repeated contexts will be used.
     * Example: "groupId,artifactId,version,scope,type"
     *
     * @since 4.0.0
     */
    @Config

     * build a smaller set of projects but perform other operations in the context of your reactor.
     */
    private List<MavenProject> allProjects;

    private MavenProject topLevelProject;

    private ProjectDependencyGraph projectDependencyGraph;

    private boolean parallel;

    /**
     * Plugin context keyed by project ({@link MavenProject#getId()}) and by plugin lookup key

        assertEquals(options, readOptions);
    }

    @Test
    @DisplayName("Test size calculation without create contexts")
    void testSizeWithoutCreateContexts() {
        request = new Smb2CreateRequest(mockConfig, "test.txt");

        int expectedSize = Smb2Constants.SMB2_HEADER_LENGTH + 56;

Prefer to set the entrypoint in `pyproject.toml` when possible.

## Use `Annotated`

Always prefer the `Annotated` style for parameter and dependency declarations.

It keeps the function signatures working in other contexts, respects the types, allows reusability.

### In Parameter Declarations

Use `Annotated` for parameter declarations, including `Path`, `Query`, `Header`, etc.:

```python
from typing import Annotated

            return queryHelper.build(searchRequestType, query, context -> {
                if (SearchRequestType.ADMIN_SEARCH.equals(searchRequestType)) {
                    context.skipRoleQuery();
                } else if (similarDocHash != null) {
                    final DocumentHelper documentHelper = ComponentUtil.getDocumentHelper();
                    context.addQuery(boolQuery -> {

TFE_Op* CloneOp(const TFE_Op* other) {
  TF_Status* status = TF_NewStatus();
  TFE_Context* context = TFE_OpGetContext(other, status);
  CHECK_EQ(TF_OK, TF_GetCode(status)) << TF_Message(status);
  const char* op_name = TFE_OpGetName(other, status);
  CHECK_EQ(TF_OK, TF_GetCode(status)) << TF_Message(status);
  TFE_Op* ret = TFE_NewOp(context, op_name, status);
  CHECK_EQ(TF_OK, TF_GetCode(status)) << TF_Message(status);