{"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","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","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 ?","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","offTopic":true}],"breakdown":[{"sourceKey":"github","sourceName":"GitHub","count":4}],"total":4}}