graphprotocol / graphprotocol/graph-node
`graphman rewind --start-block <deployment_id>` command not working on v0.35.1
Open
Nobody has claimed this yet.
bug
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
It looks like the --start-block flag on the graphman rewind command isn't working on v0.35.1
This was working fine in previous versions like 0.35.0
I am pasting an example below:
Relevant log output
graphman rewind --start-block QmbJrDawxWmkxPGuNQcyB5owdGUbNZTFeYKt5d222Ug9jX
error: the following required arguments were not provided:
--block-hash <BLOCK_HASH>
--block-number <BLOCK_NUMBER>
Usage: graphman --config <CONFIG> rewind --start-block --block-hash <BLOCK_HASH> --block-number <BLOCK_NUMBER> <DEPLOYMENTS>...
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
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
Start by reproducing graphman rewind --start-block <deployment_id> on v0.35.1 and compare its argument parsing with v0.35.0. Trace the graphman rewind entry point and verify that the command accepts the deployment ID without incorrectly requiring --block-hash and --block-number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100