public final int getFlags() {
        return this.flags;
    }

    /**
     * Adds the specified flags to this message.
     *
     * @param flag the flags to add
     */
    public final void addFlags(final int flag) {
        this.flags |= flag;
    }

    /**
     * Clears the specified flags from this message.
     *
     * @param flag the flags to clear
     */

        void testSplit() {
            TestServerMessageBlock2Request nextRequest = new TestServerMessageBlock2Request(mockConfig);
            nextRequest.addFlags(SMB2_FLAGS_RELATED_OPERATIONS);
            testRequest.setNext(nextRequest);

            CommonServerMessageBlockRequest result = testRequest.split();

            assertSame(nextRequest, result);

    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.internal.RequestWithPath#setResolveInDfs(boolean)
     */
    @Override
    public void setResolveInDfs(final boolean resolve) {
        addFlags(SMB2_FLAGS_DFS_OPERATIONS);
        this.resolveDfs = resolve;
    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.internal.RequestWithPath#isResolveInDfs()
     */
    @Override

instead of `add-dir-header`). Fixing this included cleaning up flag handling in component-base/logs: that package no longer adds flags to the global flag sets. Commands which want the klog and `--log-flush-frequency` flags must explicitly call `logs.AddFlags`; the new `cli.Run` does that for commands. That helper function also covers flag normalization and printing of usage and errors in a consistent way (print usage text first if parsing failed, then the error). ([#105076](https://github.com/kubern...