Docs: 2026.07.1 release notes and the 2026.06.0 dispatcher crash loop - #3
Merged
Conversation
Anyone upgrading from 2026.06.0 today gets a platform that accepts jobs and runs none of them, with only "not enough available capacity" to explain it. Document both conditions that have to hold for the default queue to work, the verified workaround, and the fact that the workaround does not survive a restart of forail-task. Also spell out that role assignments lost to the 2026.06.0 bug are not recreated by the upgrade.
Measured on a fresh 2026.06.0 install while validating the upgrade path: the dispatcher exits every ~50s on the unconditional 30s observability schedule, because the task carries Celery's @shared_task rather than Forail's @task(). Every job in flight is cancelled with it, so the release cannot run a job at all. It was fixed in this release without being written down, which left the strongest reason to upgrade undocumented.
A patch release with one purpose: an upgrade no longer leaves a platform that accepts jobs and runs none of them. Also marks the known issue in the 2026.07.0 notes as fixed, and points at the release rather than the workaround.
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.
update_active_jobs_gauge_taskevery 30 s unconditionally, but in that release the function carries Celery's@shared_taskinstead of Forail's@task(). The dispatcher raisesValueError, exits, and cancels whatever is running. Measured on a fresh install: one crash every ~50 s, indefinitely. It was fixed in 2026.07.0 without being written down, which left the strongest reason to upgrade undocumented.