graphprotocol / graphprotocol/indexer
Can't create allocation to subgraph with deleted graft base
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
I have synced subgraph and then removed graft base. Now indexer agent tries to deploy subgraph before it creates allocation, and fails because of graft.
Add checking for subgraph status before deploying it to node please.
Contributor guide
No contributing guide indexed for this repository
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 tracing the indexer agent's deployment and allocation flow for a synced subgraph whose graft base has been deleted. Identify where deployment occurs relative to allocation creation and determine how subgraph status should be checked before deployment. Done means this scenario no longer attempts the failing deployment and the allocation flow handles the deleted graft base safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100