Guillaume Nodet <******@****.***> 1729859506 +0200

Guillaume Nodet <******@****.***> 1729859506 +0200

 - Support for the seccomp annotations `seccomp.security.alpha.kubernetes.io/pod` and `container.seccomp.security.alpha.kubernetes.io/[name]` has been deprecated since 1.19, will be dropped in 1.25. Transition to using the `seccompProfile` API field. ([#104389](https://github.com/kubernetes/kubernetes/pull/104389), [@saschagrunert](https://github.com/saschagrunert))

        Key key = new Key(project, transitive, false);
        // Do not use computeIfAbsent here, as the computation is recursive
        // and this is not supported by computeIfAbsent.
        List<MavenProject> list = cache.get(key);
        if (list == null) {
            list = applyFilter(projectDependencyGraph.getDownstreamProjects(project, transitive), transitive, false);

    }

    @BeforeEach
    void setUp() {
        transaction = new TestSmbComTransaction();
        transaction.command = ServerMessageBlock.SMB_COM_TRANSACTION;
        transaction.name = "\\PIPE\\test";
        transaction.txn_buf = new byte[1024];
        transaction.maxBufferSize = 1024;
    }

    @Test
    @DisplayName("Test reset() method resets transaction state")
    void testReset() {
        // Modify state

The reasoning for this rule is, that such additional abbr elements are manually added by the human editor of the translation, in order to translate or explain an English word to the human readers of the translation. These additional abbr elements would not make sense in the English text, but they do make sense in the translation. So keep them in the translation, even though they are not part of the English text. This rule only applies to abbr elements.

- Apply above rules also when there...

        // Set up transaction with zero data
        transaction.setTotalParameterCount(100);
        transaction.setTotalDataCount(0);
        transaction.setMaxParameterCount(1024);
        transaction.setMaxDataCountForTest(2048);
        transaction.setParameterCount(100);
        transaction.setParameterOffset(80);
        transaction.setDataCount(0);
        transaction.setDataOffset(0);

    }

    /**
     * Makes dependencies non-transitive.
     * <p>
     * Gradle allows setting all dependencies as non-transitive very easily.
     * Sadly this mechanism does not translate into maven pom generation. In order
     * to effectively make the pom act as if it has no transitive dependencies,
     * we must exclude each transitive dependency of each direct dependency.
     * <p>

    void testNextElement() {
        transaction.setMaxBufferSize(4096);
        transaction.setBuffer(new byte[SmbComTransaction.TRANSACTION_BUF_SIZE]);
        transaction.setParametersWireFormatReturn(100);
        transaction.setDataWireFormatReturn(200);

        SmbComTransaction result = transaction.nextElement();

        assertSame(transaction, result);
    }

    @Test

* Retranslate, having the good translation in place. The ideal result would be that the LLM makes no changes anymore to the translation. That means that the general prompt and your language specific prompt are as good as they can be (It will sometimes make a few seemingly random changes, the reason is that [LLMs are not deterministic algorithms](https://doublespeak.chat/#/handbook#deterministic-output)).