graphprotocol / graphprotocol/indexer
Unable to close allocations and allocate to the same subgraph using the old method (graph indexer allocations create/close)
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
After closing the allocation the first time on the same epoch, can't allocate back to the same subgraph
graph indexer allocations create/close
[GraphQL] Failed to allocate: allocation ID already exists on chain
But using action queue countless times works
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 reproducing the issue with graph indexer allocations create/close on the same subgraph and epoch, then compare it with the action queue flow that succeeds. Done means an allocation can be closed and recreated for the same subgraph without the on-chain “allocation ID already exists” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- blockchain, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100