Repository navigation
release: publish v0.133.1-pre2.1 stability fixes - #88
Merged
Merged
Conversation
added 30 commits
October 7, 2026 19:39
Keep the original serving identity while a bounded observation is pending. Track actual quorum and storage losses so a later READY sample cannot revive an interrupted boot. Classify failed clocks separately and keep resource admission reads nonblocking. Preserve shutdown diagnostics and data guards.
…ling Exercise the original accepted-cohort capture with only a later quorum or storage observation changed. Both cases preserve the expected formation generation and fail on the legacy qualification projection.
added 4 commits
October 8, 2026 20:43
Use a fixed in-place shared allocation pool for resource owners and queues. Preserve complete conflict, grant, cancellation and cleanup identities as capacity grows, and size message queues from the same startup inputs. Keep allocation outside entry spinlocks, preserve grant delivery during projection memory pressure, and cover pool exhaustion, reclamation, callback cleanup and full release/retirement batches.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release the accepted PRE2 stability revision as
v0.133.1-pre2.1.Exact release source:
2d857abffc76a5cbfbc1b01c7d99b82ab0375f46.This revision fixes transient admission and checkpoint/configuration publication errors, concurrent connection failures, same-table lock capacity limits, cross-node row-lock wait errors, and slow repeated cross-node reads.
Acceptance covers four Linux ARM64 VMs with GFS2 and O_DIRECT, 50,000 rows, 8 and 16 clients per node, 180 seconds at 16 clients per node, two normal full stops, one restart using the same data, and identical full-row results on all four nodes. The assertion-enabled build measured about 98 aggregate TPS in the sustained window; this is an environment-specific result. 32/64 clients per node remain unqualified. Shared dirty-page handoff without a pre-handoff write (W06) remains disabled.
Existing exact-source qualification:
The repository owner explicitly authorized an ordinary administrator merge commit, preserving history. Only the pull-request-only historical commit-subject format check is waived, following #87. No build, test, static-analysis, timeout, or data-consistency requirement is waived. Release-branch fast-gate and this PR's remaining checks are verified before merging. The annotated release tag will point to the exact source commit above, and publishing follows a successful tag-triggered nightly run.
PR check result: 37797191612 failed only the waived
Lint commit messagestep (6 historical subjects); all preceding Validate checks succeeded. Its four dependent jobs were skipped and are not counted as passes. The unchanged full fast-gate is running on this exact release-branch commit as 37797192333; merge awaits its actual five-job success.Release-branch fast-gate 37797192333, attempt 2, is now SUCCESS 5/5 on exact
2d857abffc76a5cbfbc1b01c7d99b82ab0375f46. The first macOS attempt exceeded its unchanged 12-minute job limit; only that job was rerun and actually passed. All original results are retained. No timeout or acceptance threshold was changed.