-
Notifications
You must be signed in to change notification settings - Fork 46
fix(wrap): resolve DM participants for correct routing #644
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
+179
−61
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
10248c3
fix(wrap): resolve DM participants instead of broadcasting to all agents
khaliqgant f3ecbc7
fix(wrap): filter out presence and reaction events from PTY injection
khaliqgant 0f476f3
fix: consolidate duplicate DM participant resolution into helpers
khaliqgant a881c5e
fix: centralize agent name comparison and DM cache across wrap.rs and…
khaliqgant 44b5e6a
fix: use case-insensitive comparison for self-echo agent ID check
khaliqgant 9bece94
style: auto-format Rust code with cargo fmt
github-actions[bot] 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
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
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.
🟡 Error results from DM participant resolution are no longer cached, enabling API call storms under sustained failures
The old
resolve_dm_participantsinsrc/main.rs:5256-5270unconditionally cached the result (includingvec![]fromunwrap_or_elseon error) for the 30-second TTL. The newresolve_dm_participants_cachedonly caches on theOkpath (src/helpers.rs:1055) and skips caching entirely onErr(src/helpers.rs:1058-1068). This means that when the DM participants API is failing (network issue, outage, etc.), every incoming DM for the same conversation-ID will trigger a fresh API call instead of being throttled by the 30-second TTL. Under sustained failures with many DMs, this can multiply failed API requests significantly compared to the old behaviour, which capped retries at roughly one per TTL window per conversation.Was this helpful? React with 👍 or 👎 to provide feedback.