Repository navigation
Qualify the published four-worker queue consumer on 2.5.32 - #837
Merged
Merged
Conversation
|
rmcdaniel
marked this pull request as ready for review
October 17, 2026 21:35
Member
Author
|
Fresh main The ordinary published four-worker pass remains its own candidate original |
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
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.



Qualify normally installed Workflow 2.5.32 /
78075b6fwith the existingcontinuous four-worker consumer on stock hosted PHP 8.3.
Every other locked package object is unchanged.
original deadlines and aggregate 2-CPU / 2-GiB / no-swap limits.
Bounded failure diagnostics capture row state, native error information and
admission timing. They do not alter runtime behavior or grant task authority.
Published 2.5.32 passes all 17 release-verification jobs and the six normal
installed regressions / 92 assertions, with all 939 runtime/resource files
matching its immutable tag. Source #838 and compatible backport #839 are merged.
Earlier outcomes remain explicit:
7789fc95, run 39064714553, original01m55q38dd5jr78nse8e2vseqd: business assertions pass, one repair fails theclean guard. No delivery exception was captured.
3183e877, run 39065805820: ordinary and diagnostic originals bothcomplete all callbacks once, but each retains a failed pre-claim SQLite5
delivery. Reserved-row observations are pre-update intents, not commit proof.
e3a04c22, run 39070006619: ordinary original01m55vckqxdz5ccksvk4cswm9zcompletes all 64 callbacks once, with exact output,prefix and deadlines, but retains one failed pre-claim SQLite5 delivery and
one repair. Its task
01m55vcm0nr46tc7gwc1tyvn01has one logical attempt.The fresh diagnostic original
01m55ve07aekzbvq2ek990psttpasses the unchangedclean guard. The failed ordinary record stays failed; its precise native error
type and admission elapsed time were not captured, so its cause is not settled.
c903ee31, run 39071079709: the fresh ordinary cohortpasses all unchanged guards; the failure-only diagnostic is skipped. Normal
source, Sonar and boundary checks also pass. This result does not explain or relabel the
earlier failed original, and no further runtime correction is claimed.
The documented repair policy intentionally retains reserved deliveries on its
repair path. That fact does not waive the current clean-consumer criterion.
Merged as
a5c0ce94a4bdf66b2c874dce4ea910b16988208c, whole tree1749ff19ff17cd9acc34d312dcb6e10eb8e3b25f, exactly the qualified candidate.Parents are qualified main
8f55cdfband final candidatec903ee31.The merged remote head is absent.