fix(bot): restore dashboard ticket bridge after queue merge - #13
Open
OfficialAbhinavSingh wants to merge 5 commits into
Open
OfficialAbhinavSingh wants to merge 5 commits into
OfficialAbhinavSingh wants to merge 5 commits into
Conversation
This was referenced Sep 28, 2026
…9-29 docs(bot): refresh bridge status and setup guide
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.
After the async queue merge,
/tickets/create-threadis registered on a legacy request model, so dashboard ticket creation receives HTTP 422. The same merge initializes Firestore during module import, which crashes CI without credentials, and queue workers can stay bound to a previous event loop after restart.This restores the ticket handler and its compatibility aliases, keeps Firestore initialization lazy, and drains/cancels queue workers before resetting their queues for a new lifecycle. A regression test covers queue reuse across event loops.
Validation:
uv run --locked python -m unittest discover -s tests -v(37 passed),uv run --locked python -m compileall -q cogs utils server.py, andgit diff --check.