graphprotocol / graphprotocol/graph-node
Smarter provider choice and fallback between providers
Open
Nobody has claimed this yet.
hardening
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
- Ensure subgraphs are assigned to a provider that supports its features (if available)
- Support switching providers if issues with currently assigned provider
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 mapping where subgraph provider assignment and provider failures are handled, then identify the existing tests around those paths. Done means providers are selected according to supported features and can be switched when the assigned provider has issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100