NotASithLord / NotASithLord/peerd
A2A ask can lose fast replies and ignore Stop during send
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 45
- Avg merge
- 11d 5h
- Merged PRs (30d)
- 1
Description
Problem
The A2A ask path registers its reply correlation after it waits for sendDm. A fast peer reply can arrive first and be dropped. A stalled send can also keep dispatch() pending after the reply timeout or Stop clears the correlation.
Expected
- Register the correlation before send.
- Let send and reply handling run together.
- Let a reply, timeout, or Stop settle the call while the transport is pending.
- Ignore late transport settlement after the ask has settled.
- Keep peer identity checks and cleanup unchanged.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the A2A ask path and its dispatch() flow, then trace sendDm and reply-correlation registration. Confirm that correlation is registered before sending and that reply, timeout, or Stop can settle the call while transport remains pending; verify peer identity checks and cleanup stay unchanged and late transport settlement is ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100