Multistream targets should get propagated to Mist server immediately, not waiting for stream restart
Open
Nobody has claimed this yet.
tech debt
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
But we _shouldn't_ just make an HTTP request to the current Mist target in the database; not super reliable. Some kind of Rabbit/Analyzer scheme here.
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
No files, tests, or entry points are named. Start by tracing how multistream targets reach the Mist server and where updates currently wait for a stream restart; the issue specifically rejects an HTTP request to the current database target and points to a Rabbit/Analyzer scheme. Done means target changes propagate immediately without a stream restart, with the reliability behavior agreed and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rabbitmq, typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100