return val
}

func setCaller(ctx context.Context, cl *RemoteClient) context.Context {
	//nolint:staticcheck // SA1029 Staticcheck is drunk.
	return context.WithValue(ctx, ctxCallerKey{}, cl)
}

func setSubroute(ctx context.Context, s string) context.Context {
	//nolint:staticcheck // SA1029 Staticcheck is drunk.
	return context.WithValue(ctx, ctxSubrouteKey{}, s)
}

        // Negotiate context offset (0 for non-3.1.1)
        SMBUtil.writeInt4(0, buffer, 60);

        return buffer;
    }

    /**
     * Creates a larger buffer suitable for testing negotiate contexts.
     */
    private byte[] createLargeBufferForContexts() {
        byte[] buffer = new byte[1024]; // Large enough for contexts

        // Copy basic structure

            // Arrange
            NegotiateContextResponse[] contexts =
                    new NegotiateContextResponse[] { new PreauthIntegrityNegotiateContext(), new EncryptionNegotiateContext() };

            // Act & Assert
            for (NegotiateContextResponse context : contexts) {
                assertNotNull(context);
                assertTrue(context.getContextType() > 0);
            }
        }
    }

            context = SingletonContext.getInstance().withCredentials(auth);
        } catch (Exception e) {
            log.warn("Failed to create authenticated context, trying guest access", e);
            context = SingletonContext.getInstance();
        }

     *
     * @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;
    }

    /**

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...

}

func rebalanceLogIf(ctx context.Context, err error, errKind ...any) {
	logger.LogIf(ctx, "rebalance", err, errKind...)
}

func rebalanceLogEvent(ctx context.Context, msg string, args ...any) {
	logger.Event(ctx, "rebalance", msg, args...)
}

func adminLogIf(ctx context.Context, err error, errKind ...any) {
	logger.LogIf(ctx, "admin", err, errKind...)
}

func authNLogIf(ctx context.Context, err error, errKind ...any) {

        UpgradeContext context = TestUtils.createMockContext(Paths.get("/test"));

        // Test indentation methods don't throw exceptions
        context.indent();
        context.indent();
        context.info("Indented message");

        context.unindent();
        context.unindent();
        context.unindent(); // Should not go below 0
        context.info("Unindented message");
    }

    @Test

        // Test constructor when signing is enabled
        NtlmContext context = new NtlmContext(mockAuth, true);
        assertNotNull(context);
        assertFalse(context.isEstablished());
        assertNull(context.getServerChallenge());
        assertNull(context.getSigningKey());
        assertNull(context.getNetbiosName());

     * 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