{"data":{"items":[{"id":"6a513d85-4bdf-4e67-92e1-c3ac3cc0d2b9","excerpt":"[#18095] Flaky test: org.infinispan.partitionhandling.NumOwnersNodeCr… — …ashInSequenceTest#testNodeCrashedBeforeStFinished\r\n\r\nCloses: #18095\r\n\r\nAuthor Checklist (all must be checked):\r\n- [ ] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. c","url":"https://github.com/infinispan/infinispan/pull/18167","role":"pain","weight":0.9024239,"occurredAt":"2026-09-22T22:33:52.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.5314286,"sentiment":-0.42857143,"confidence":0.58926934,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18095] Flaky test: org.infinispan.partitionhandling.NumOwnersNodeCr…","body":"…ashInSequenceTest#testNodeCrashedBeforeStFinished\r\n\r\nCloses: #18095\r\n\r\nAuthor Checklist (all must be checked):\r\n- [ ] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\r\n- [ ] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\r\n- [ ] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\r\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\r\n- [ ] Log messages of level `INFO` and above have been internationalized.\r\n- [ ] If the PR affects performance, include before/after benchmarks.\r\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\r\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\r\n\r\nReviewer Checklist (all must be checked):\r\n- [ ] Code review\r\n  - Are the changes reasonable?\r\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\r\n  - Is the code understandable? (KISS, comments)\r\n  - Is there a better way to implement/write the functionality, code pieces?\r\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\r\n- [ ] Test review\r\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\r\n  - Does the base functionality works as expected in the build project?\r\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\r\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\r\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\r\n- [ ] Documentation review\r\n  - Does the new/changed documentation cover the PR in sufficient matter?\r\n  - For public API, are JavaDocs included for every new/changed class/method ?\r\n  - For new features, does the documentation add/amend any usage examples ?\r\n  - Grammar and syntax checks \r\n  - Does AsciiDoc generation report any WARN messages ?\r\n","authorHash":"1ab76f6f86549f43604600ea7bfdd611","rating":null,"offTopic":true},{"id":"2bab0fb0-d0c3-41b2-bdd2-314fc2e7497e","excerpt":"[#18120] Flaky test: org.infinispan.conflict.impl.SegmentHashStoreCon… — …flictManagerTest#testUpdateWithStoreBackedOldValue\r\n\r\nCloses: #18120\r\n\r\nAuthor Checklist (all must be checked):\r\n- [ ] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. ","url":"https://github.com/infinispan/infinispan/pull/18124","role":"pain","weight":0.9024239,"occurredAt":"2026-09-17T02:26:03.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.5314286,"sentiment":-0.42857143,"confidence":0.58926934,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18120] Flaky test: org.infinispan.conflict.impl.SegmentHashStoreCon…","body":"…flictManagerTest#testUpdateWithStoreBackedOldValue\r\n\r\nCloses: #18120\r\n\r\nAuthor Checklist (all must be checked):\r\n- [ ] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\r\n- [ ] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\r\n- [ ] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\r\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\r\n- [ ] Log messages of level `INFO` and above have been internationalized.\r\n- [ ] If the PR affects performance, include before/after benchmarks.\r\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\r\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\r\n\r\nReviewer Checklist (all must be checked):\r\n- [ ] Code review\r\n  - Are the changes reasonable?\r\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\r\n  - Is the code understandable? (KISS, comments)\r\n  - Is there a better way to implement/write the functionality, code pieces?\r\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\r\n- [ ] Test review\r\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\r\n  - Does the base functionality works as expected in the build project?\r\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\r\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\r\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\r\n- [ ] Documentation review\r\n  - Does the new/changed documentation cover the PR in sufficient matter?\r\n  - For public API, are JavaDocs included for every new/changed class/method ?\r\n  - For new features, does the documentation add/amend any usage examples ?\r\n  - Grammar and syntax checks \r\n  - Does AsciiDoc generation report any WARN messages ?\r\n","authorHash":"1ab76f6f86549f43604600ea7bfdd611","rating":null,"offTopic":true},{"id":"ece5c90d-37f1-49ef-8bb2-90b58ce1dc46","excerpt":"[#18413] Concurrent local reindex fails on clustered lock — * Disjoint a local indexer from a cluster-wide indexer. No more interleaving between local indexers.\n\nCloses: #18413\n\n---\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/","url":"https://github.com/infinispan/infinispan/pull/18416","role":"pain","weight":0.89206314,"occurredAt":"2026-11-03T21:56:35.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.51384616,"sentiment":-0.3846154,"confidence":0.58926934,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18413] Concurrent local reindex fails on clustered lock","body":"* Disjoint a local indexer from a cluster-wide indexer. No more interleaving between local indexers.\n\nCloses: #18413\n\n---\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [x] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [ ] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?\n","authorHash":"64708ef36cbef61648aaba84091355d9","rating":null,"offTopic":true},{"id":"7e0a49bf-890f-49a3-9ac8-09e0007130d9","excerpt":"[#13535] Fix flaky IracRestartWithoutGlobalStateTest — The idea is to stop the nodes in order to ensure the version isn't lost. This behaviour is already in the documentation, which recommends using persistent state to store the versions.\n\nCloses: #13535\n\nAuthor Checklist (all must be checked):\n- [x] Commit message inc","url":"https://github.com/infinispan/infinispan/pull/18420","role":"pain","weight":0.8547924,"occurredAt":"2026-11-03T22:09:58.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.5314286,"sentiment":-0.42857143,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#13535] Fix flaky IracRestartWithoutGlobalStateTest","body":"The idea is to stop the nodes in order to ensure the version isn't lost. This behaviour is already in the documentation, which recommends using persistent state to store the versions.\n\nCloses: #13535\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [x] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [ ] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?\n","authorHash":"64708ef36cbef61648aaba84091355d9","rating":null,"offTopic":true},{"id":"4a7b9d4f-a9a4-496f-8f7e-731fab7f7895","excerpt":"[16.0.x] [#18266] RESP PING returns bulk string — **Backport:** https://github.com/infinispan/infinispan/pull/18267\r\n\r\n```\r\n0000   00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00   ..............E.\r\n0010   00 3b ef 21 40 00 40 06 4d 99 7f 00 00 01 7f 00   .;.!@.@.M.......\r\n0020   00 01 2b d6 b6 b2 0c cb f0 a7 af 99 2e ","url":"https://github.com/infinispan/infinispan/pull/18291","role":"pain","weight":0.84790707,"occurredAt":"2026-10-12T09:49:25.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.6037313,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[16.0.x] [#18266] RESP PING returns bulk string","body":"**Backport:** https://github.com/infinispan/infinispan/pull/18267\r\n\r\n```\r\n0000   00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00   ..............E.\r\n0010   00 3b ef 21 40 00 40 06 4d 99 7f 00 00 01 7f 00   .;.!@.@.M.......\r\n0020   00 01 2b d6 b6 b2 0c cb f0 a7 af 99 2e d2 80 18   ..+.............\r\n0030   00 40 fe 2f 00 00 01 01 08 0a 18 9d e0 16 60 5f   .@./..........`_\r\n0040   73 76 2b 50 4f 4e 47 0d 0a                        sv+PONG..\r\n```\r\n\r\nCloses: #18266\r\n\r\n---\r\n\r\nAuthor Checklist (all must be checked):\r\n- [ ] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\r\n- [ ] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\r\n- [ ] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\r\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\r\n- [ ] Log messages of level `INFO` and above have been internationalized.\r\n- [ ] If the PR affects performance, include before/after benchmarks.\r\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\r\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\r\n\r\nReviewer Checklist (all must be checked):\r\n- [ ] Code review\r\n  - Are the changes reasonable?\r\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\r\n  - Is the code understandable? (KISS, comments)\r\n  - Is there a better way to implement/write the functionality, code pieces?\r\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\r\n- [ ] Test review\r\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\r\n  - Does the base functionality works as expected in the build project?\r\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\r\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\r\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\r\n- [ ] Documentation review\r\n  - Does the new/changed documentation cover the PR in sufficient matter?\r\n  - For public API, are JavaDocs included for every new/changed class/method ?\r\n  - For new features, does the documentation add/amend any usage examples ?\r\n  - Grammar and syntax checks \r\n  - Does AsciiDoc generation report any WARN messages ?\r\n","authorHash":"a89cebf7d41f7fffdad21b107a83dd4a","rating":null,"offTopic":true},{"id":"c737481b-1b36-4b4b-aba8-a9a8b44010b9","excerpt":"[#18411] Server test suite should allow using podman or docker — Closes: #18411\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted accord","url":"https://github.com/infinispan/infinispan/pull/18421","role":"pain","weight":0.8436937,"occurredAt":"2026-11-03T22:53:10.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.60073125,"matchedPatterns":["missing_feature","product:docker"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18411] Server test suite should allow using podman or docker","body":"Closes: #18411\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [ ] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [ ] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?\n","authorHash":"1ab76f6f86549f43604600ea7bfdd611","rating":null,"offTopic":true},{"id":"8d4d469d-90bc-4cbb-9973-7e953c514f4a","excerpt":"[#18287] Avoid lost sequence number on topology change — Every sequence number that is handed out to a backup stream is followed by either a `BackupWriteCommand` or a `BackupNoopCommand` for the same segment and topology id. A failed or outdated write must not leave a gap that blocks later writes on the segment.\n\nClose","url":"https://github.com/infinispan/infinispan/pull/18288","role":"pain","weight":0.83352894,"occurredAt":"2026-10-10T10:28:20.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.49333334,"sentiment":-0.33333334,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18287] Avoid lost sequence number on topology change","body":"Every sequence number that is handed out to a backup stream is followed by either a `BackupWriteCommand` or a `BackupNoopCommand` for the same segment and topology id. A failed or outdated write must not leave a gap that blocks later writes on the segment.\n\nCloses: #18287 \n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [x] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [x] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?\n","authorHash":"51cb600c8ca0ab8d170aac71147fdd37","rating":null,"offTopic":false},{"id":"71acbd91-7515-4cfd-a4e0-7569d14c3cca","excerpt":"[#17934] Add ClassAllowList and untrusted class loading tests — Closes #17934\n\n\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\n<!--- Closes: #000","url":"https://github.com/infinispan/infinispan/pull/18361","role":"pain","weight":0.82759607,"occurredAt":"2026-10-23T10:47:30.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.58926934,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#17934] Add ClassAllowList and untrusted class loading tests","body":"Closes #17934\n\n\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\n<!--- Closes: #00000 -->\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [ ] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?","authorHash":"1ac11ac5062f7b12a1def0cc76a67f7a","rating":null,"offTopic":true},{"id":"997e0136-1c25-4924-a25e-b6eb7410128c","excerpt":"[16.0.x] [#18264] Generate entry versions for REST operations — Closes: #18264\n\nBackport of https://github.com/infinispan/infinispan/pull/18265\n\n---\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.","url":"https://github.com/infinispan/infinispan/pull/18362","role":"pain","weight":0.7839141,"occurredAt":"2026-10-23T12:08:04.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[16.0.x] [#18264] Generate entry versions for REST operations","body":"Closes: #18264\n\nBackport of https://github.com/infinispan/infinispan/pull/18265\n\n---\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [ ] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?\n","authorHash":"64708ef36cbef61648aaba84091355d9","rating":null,"offTopic":true},{"id":"3c074cbc-f704-4247-bc75-701c730e2631","excerpt":"[#18300] Fix rolling upgrade default FROM version — Closes #18300\n\n\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\n<!--- Closes: #00000 -->\n\nAuth","url":"https://github.com/infinispan/infinispan/pull/18302","role":"pain","weight":0.7839141,"occurredAt":"2026-10-14T11:41:46.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18300] Fix rolling upgrade default FROM version","body":"Closes #18300\n\n\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\n<!--- Closes: #00000 -->\n\nAuthor Checklist (all must be checked):\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\n- [ ] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\n- [ ] Log messages of level `INFO` and above have been internationalized.\n- [ ] If the PR affects performance, include before/after benchmarks.\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\n\nReviewer Checklist (all must be checked):\n- [ ] Code review\n  - Are the changes reasonable?\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\n  - Is the code understandable? (KISS, comments)\n  - Is there a better way to implement/write the functionality, code pieces?\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\n- [ ] Test review\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\n  - Does the base functionality works as expected in the build project?\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\n- [ ] Documentation review\n  - Does the new/changed documentation cover the PR in sufficient matter?\n  - For public API, are JavaDocs included for every new/changed class/method ?\n  - For new features, does the documentation add/amend any usage examples ?\n  - Grammar and syntax checks \n  - Does AsciiDoc generation report any WARN messages ?","authorHash":"1ac11ac5062f7b12a1def0cc76a67f7a","rating":null,"offTopic":true},{"id":"39a4ed28-4bef-45f3-b982-5798e3d1719f","excerpt":"[#18242] Reuse test clusters across methods in HotRod upgrade tests — Closes #18242\r\n\r\n\r\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\r\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\r\n<!--- C","url":"https://github.com/infinispan/infinispan/pull/18243","role":"pain","weight":0.7839141,"occurredAt":"2026-10-01T11:03:27.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[#18242] Reuse test clusters across methods in HotRod upgrade tests","body":"Closes #18242\r\n\r\n\r\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\r\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\r\n<!--- Closes: #00000 -->\r\n\r\nAuthor Checklist (all must be checked):\r\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\r\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\r\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\r\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\r\n- [ ] Log messages of level `INFO` and above have been internationalized.\r\n- [ ] If the PR affects performance, include before/after benchmarks.\r\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\r\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\r\n\r\nReviewer Checklist (all must be checked):\r\n- [ ] Code review\r\n  - Are the changes reasonable?\r\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\r\n  - Is the code understandable? (KISS, comments)\r\n  - Is there a better way to implement/write the functionality, code pieces?\r\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\r\n- [ ] Test review\r\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\r\n  - Does the base functionality works as expected in the build project?\r\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\r\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\r\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\r\n- [ ] Documentation review\r\n  - Does the new/changed documentation cover the PR in sufficient matter?\r\n  - For public API, are JavaDocs included for every new/changed class/method ?\r\n  - For new features, does the documentation add/amend any usage examples ?\r\n  - Grammar and syntax checks \r\n  - Does AsciiDoc generation report any WARN messages ?","authorHash":"1ac11ac5062f7b12a1def0cc76a67f7a","rating":null,"offTopic":true},{"id":"e21fb833-66f9-42ae-9925-b445b1545bf0","excerpt":"[16.0.x] [#18140] Allow any command while in the subscribed state — **Backport:** https://github.com/infinispan/infinispan/pull/18141\r\n\r\nCloses #18140\r\n\r\n\r\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\r\n<!--- All code change PRs should re","url":"https://github.com/infinispan/infinispan/pull/18166","role":"pain","weight":0.7839141,"occurredAt":"2026-09-22T21:41:39.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"[16.0.x] [#18140] Allow any command while in the subscribed state","body":"**Backport:** https://github.com/infinispan/infinispan/pull/18141\r\n\r\nCloses #18140\r\n\r\n\r\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\r\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\r\n<!--- Closes: #00000 -->\r\n\r\nAuthor Checklist (all must be checked):\r\n- [x] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\r\n- [x] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\r\n- [x] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\r\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\r\n- [ ] Log messages of level `INFO` and above have been internationalized.\r\n- [ ] If the PR affects performance, include before/after benchmarks.\r\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\r\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\r\n\r\nReviewer Checklist (all must be checked):\r\n- [ ] Code review\r\n  - Are the changes reasonable?\r\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\r\n  - Is the code understandable? (KISS, comments)\r\n  - Is there a better way to implement/write the functionality, code pieces?\r\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\r\n- [ ] Test review\r\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\r\n  - Does the base functionality works as expected in the build project?\r\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\r\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\r\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\r\n- [ ] Documentation review\r\n  - Does the new/changed documentation cover the PR in sufficient matter?\r\n  - For public API, are JavaDocs included for every new/changed class/method ?\r\n  - For new features, does the documentation add/amend any usage examples ?\r\n  - Grammar and syntax checks \r\n  - Does AsciiDoc generation report any WARN messages ?","authorHash":"a89cebf7d41f7fffdad21b107a83dd4a","rating":null,"offTopic":true},{"id":"2eca7b4f-bfdb-45e8-962f-1edcf49c568e","excerpt":"Remove TODO for SELECTIVE NearCacheMode — Removed TODO comment regarding SELECTIVE mode, since bloom filter-assisted near caching was implemented in ISPN-10216\r\n\r\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\r\n<!--- All code change PRs sh","url":"https://github.com/infinispan/infinispan/pull/18145","role":"pain","weight":0.7839141,"occurredAt":"2026-09-21T09:19:18.000Z","sourceKey":"github","sourceName":"GitHub","credibility":0.78,"venue":"infinispan/infinispan","intent":"feature_request","painScore":0.40444446,"sentiment":-0.11111111,"confidence":0.5581667,"matchedPatterns":["missing_feature","source:github"],"statement":"(Valid and invalid, missing, partial) - Are there integrations to be considered?","title":"Remove TODO for SELECTIVE NearCacheMode","body":"Removed TODO comment regarding SELECTIVE mode, since bloom filter-assisted near caching was implemented in ISPN-10216\r\n\r\n<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->\r\n<!--- All code change PRs should relate to an issue, reference it here; see example below -->\r\n<!--- Closes: #00000 -->\r\n\r\nAuthor Checklist (all must be checked):\r\n- [ ] Commit message includes a reference to the corresponding [GitHub issue](https://github.com/infinispan/infinispan/issues) (e.g. commit message: \"[#00000] Issue title...\") and is formatted according to our [git message template](https://github.com/infinispan/infinispan/blob/main/.gitmessage).\r\n- [ ] Commits have been squashed into self-contained units of work (e.g. 'WIP'- and 'Implements feedback'-style messages have been removed).\r\n- [ ] The PR includes new/modified unit and integration tests that exercise the changes. Include additional manual testing instructions if necessary. If the PR does not include tests, clear justification **MUST** be provided.\r\n- [ ] The PR includes new/modified documentation. If the PR does not require documentation changes, clear justification **MUST** be provided.\r\n- [ ] Log messages of level `INFO` and above have been internationalized.\r\n- [ ] If the PR affects performance, include before/after benchmarks.\r\n- [ ] If the PR affects output (such as logs, CLI, Console), provide an example (text snippet/screenshot).\r\n- [ ] If the PR requires a followup or is part of a larger body of work, ensure that relevant [GitHub issues](https://github.com/infinispan/infinispan/issues) have been created to track the additional work.\r\n\r\nReviewer Checklist (all must be checked):\r\n- [ ] Code review\r\n  - Are the changes reasonable?\r\n  - Are there any use cases, integrations, inputs that haven't been considered in the implementation?\r\n  - Is the code understandable? (KISS, comments)\r\n  - Is there a better way to implement/write the functionality, code pieces?\r\n  - Is formatting in line with the rest of the project? (checkstyle and spotless)\r\n- [ ] Test review\r\n  - Is the new test coverage rich enough to cover all the changes and considerations above?\r\n  - Does the base functionality works as expected in the build project?\r\n  - Does it behave as expected when given various inputs? (Valid and invalid, missing, partial)\r\n  - Are there integrations to be considered? (Does the new functionality work well with the rest of the project, environment)\r\n  -  Even if all above works as expected, are there weird behaviors to be improved on?\r\n- [ ] Documentation review\r\n  - Does the new/changed documentation cover the PR in sufficient matter?\r\n  - For public API, are JavaDocs included for every new/changed class/method ?\r\n  - For new features, does the documentation add/amend any usage examples ?\r\n  - Grammar and syntax checks \r\n  - Does AsciiDoc generation report any WARN messages ?\r\n","authorHash":"1ac11ac5062f7b12a1def0cc76a67f7a","rating":null,"offTopic":true}],"breakdown":[{"sourceKey":"github","sourceName":"GitHub","count":13}],"total":13}}