OpenZeppelin / OpenZeppelin/Event-Scanner
Make `max_concurrent_fetches` apply to all listeners collectively, not per listener
Open
Nobody has claimed this yet.
type: bug
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
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 by reading src/event_scanner/scanner/common.rs and trace how max_concurrent_fetches is applied when multiple listeners fetch concurrently. Confirm the current per-listener behavior and identify the existing concurrency-related tests or entry points. Done means the limit is enforced collectively across all listeners, with coverage demonstrating that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100