graphprotocol / graphprotocol/indexer
Unable to close allocations on arbitrum-sepolia, sepolia chains without 0x000 and --force
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
IE069 error (local EBO subgraph is well synced and able to close other allocations as usual)
"err":"Failed to query EBO for eip155:421614's latest valid epoch number: Network not found","msg":"Epoch subgraph could not be queried"}
Had to use 0x000 and --force (true) BOTH for unallocating/reallocating only arbitrum-sepolia and sepolia chains, other unapproved chains works fine without these flags and indexer-agent will auto submit 0x000
graph indexer actions queue unallocate/reallocate --network arbitrum-one <sg> <allo_id> <allo_amount> 0x0000000000000000000000000000000000000000000000000000000000000000 true
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
No file or test is named. Start by reproducing the unallocate/reallocate actions for arbitrum-sepolia and sepolia, then trace the IE069 network lookup and EBO subgraph query; done means both chains work without requiring 0x000 and --force.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100