-
Notifications
You must be signed in to change notification settings - Fork 125
fix(cloudflare): use queue dev.id for consumer resource ID in local dev mode #1364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Mkassabov
merged 1 commit into
alchemy-run:main
from
xiaoyu2er:fix/queue-consumer-id-collision
Mar 18, 2026
+8
−1
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wouldn't we want this the other way around?
or if we know that the non-dev queue id is always going to be bad just
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
||is intentional here. In local dev mode,queue.idis""(empty string, notnull/undefined) because no Cloudflare API call is made to create the real queue.??(suggestion 1) would NOT fall back on""since nullish coalescing only triggers onnull/undefined— the bug would remain (all consumers collide on"-consumer").dev?.id(suggestion 2) would work but loses the safety fallback ifdevis somehow not set.||treats""as falsy → falls back todev.id→ each consumer gets a unique resource ID like"email-queue-consumer". This is the correct behavior.