graphprotocol / graphprotocol/indexer
indexer cli get allocations bug
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
When I execute graph indexer allocations get --status claimable I get this error:
graph@indexer-cli:~$ graph indexer allocations get --help
💁
graph indexer allocations get [options]
graph indexer allocations get [options] <allocation-id>
graph indexer allocations get [options] all
Options:
-h, --help Show usage information
-n, --network Filter allocations by their protocol network (mainnet, arbitrum-one, sepolia, arbitrum-sepolia)
--status active|closed|claimable Filter by status
--deployment <id> Fetch only allocations for a specific subgraph deployment
-o, --output table|json|yaml Choose the output format: table (default), JSON, or YAML
graph@indexer-cli:~$ graph indexer allocations get --status claimable --network arbitrum-one
✖ [GraphQL] Unsupported combination of variables provided, variables: [object Object]
graph@indexer-cli:~$ graph indexer allocations get --status claimable
✖ [GraphQL] Unsupported combination of variables provided, variables: [object Object]
[GraphQL] Unsupported combination of variables provided, variables: [object Object]
Is this outdated and the claimable option should be updated or there's a bug?
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
Reproduce the failure with graph indexer allocations get --status claimable, then trace the indexer CLI handling for the allocations get command and the GraphQL variables it sends. Done means the claimable filter works, including with --network arbitrum-one, and produces the requested allocation output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100