Fix parallel sessions killing each other via shared queue file#22
Merged
Fix parallel sessions killing each other via shared queue file#22
Conversation
queue.json was a single file per repo. When one mob's slash command wrote a queue action, the queue watcher in every running spawnAgent saw it and SIGTERM'd their agent - killing all parallel sessions, not just the one that triggered the action. Queue files are now per-mob at .codemob/queues/<mob-name>.json so each watcher only reacts to its own mob's queue.
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.
Summary
queue.jsonwas a single file per repo - when one mob wrote a queue action, the file watcher in every runningspawnAgentsaw it and SIGTERM'd all parallel sessions.codemob/queues/<mob-name>.jsonso each watcher only reacts to its own mob's queueTest plan