BF: Pin rabbitmq image to 4.2-management in test docker-compose#1841
Merged
yarikoptic-gitmate merged 1 commit intomasterfrom Apr 25, 2026
Merged
BF: Pin rabbitmq image to 4.2-management in test docker-compose#1841yarikoptic-gitmate merged 1 commit intomasterfrom
yarikoptic-gitmate merged 1 commit intomasterfrom
Conversation
The dandiarchive test stack used the floating tag `rabbitmq:management`, which began resolving to RabbitMQ 4.3.0 on 2026-04-24. CI runs started to fail. Workaround -- pin to 4.2-management to restore the previously-green behavior. Claude's unverified analytics: RabbitMQ 4.3.0 no longer permits `transient_nonexcl_queues` by default, which celery/kombu still relies on. The celery container crash-looped, assets stayed in "Pending" validation, and all Linux test jobs failed (e.g. test_publish_and_manipulate, test_get_dandiset_published*) even on unchanged master commits. Co-Authored-By: Claude Code 2.1.120 / Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1841 +/- ##
==========================================
- Coverage 76.28% 76.27% -0.01%
==========================================
Files 87 87
Lines 12484 12484
==========================================
- Hits 9523 9522 -1
- Misses 2961 2962 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
yarikoptic-gitmate
approved these changes
Apr 25, 2026
Contributor
|
@yarikoptic Can you issue a release of the CLI as soon as possible? This breakage is preventing integration tests on Note, this same issue is being fixed in |
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
3 participants
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.
The dandiarchive test stack used the floating tag
rabbitmq:management, which began resolving to RabbitMQ 4.3.0 on 2026-04-24. CI runs started to fail. Workaround -- pin to 4.2-management to restore the previously-green behavior.Claude's unverified analytics:
RabbitMQ 4.3.0 no longer permits
transient_nonexcl_queuesby default, which celery/kombu still relies on. The celery container crash-looped, assets stayed in "Pending" validation, and all Linux test jobs failed (e.g. test_publish_and_manipulate, test_get_dandiset_published*) even on unchanged master commits.