github-actions[bot] commented on PR #5359: URL: https://github.com/apache/solr/pull/5359#issuecomment-6955998797
**Automated PR readiness judgements** (LLM-generated; may be wrong; not updated on later pushes). - ✅ [Jira issue in title](https://github.com/apache/solr/blob/main/CONTRIBUTING.md): already present - ✅ [Changelog](https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc#_changelog_types_reference): type: fixed <!-- The change fixes a bug where an incomplete recovery leaves the update log in BUFFERING state, causing the transaction log to grow without bound and preventing hard commits from rolling, which is a user-visible operational issue. --> - ✅ [Reference Guide update](https://github.com/apache/solr/tree/main/solr/solr-ref-guide): not needed <!-- This is an internal bug fix in the recovery logic that does not introduce new configuration options, parameters, or user-facing behaviors that require documentation in the Reference Guide. --> - ✅ [Upgrade notes](https://github.com/apache/solr/tree/main/solr/solr-ref-guide/modules/upgrade-notes/pages): not needed <!-- The change is a bug fix that restores expected behavior (dropping the buffer on failure) and does not remove or rename any APIs, parameters, or configuration elements, nor does it change defaults in a way that requires user action. --> - ✅ Tests: included <!-- The PR modifies non-trivial production logic in `RecoveryStrategy.java` to handle state cleanup on failure paths, which warrants new tests to verify the behavior across different exit conditions (cancellation, promotion, max retries). --> <!-- Assessed commit 5423d9a7b72e67232c0851f181eb1375910f19a2 --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
