Support Epoch item for dispatchers
Open
@hongyunyan is already working on this.
Since Sep 17, 2025.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
To better handle scenarios where a dispatcher dispatches from A to B and then back to A, and to clearly distinguish between the previous and next dispatcher objects, we need to add an epoch flag to the dispatcher.
This prevents the new dispatcher from receiving event data from the old dispatcher due to a failure to cancel the old dispatcher.
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.
Assessment
This issue has not been assessed yet.