[Bug] Issue when running graph-node with `--fork-base` flag

[Eduard-Voiculescu]

Bug report

Running graph-node locally with

cargo run -- --config  ../../streamingFast/graph-node-dev/config/eth-mainnet-substreams.toml --ipfs "localhost:5001" --fork-base https://api.thegraph.com/subgraphs/id/

And then in another terminal, running a graph deploy command with

./node_modules/.bin/graph deploy --node http://127.0.0.1:8020 --ipfs http://127.0.0.1:5001 minimal --debug-fork QmZWbPvcbsULLZqWac7PkHRYXthAQvpyRj5kQjUnzGmFk1  ./subgraph.yaml

The graph-node will try to query the forked base with the wrong deployment hash. It will ignore the --debug-fork from the graph deploy command and try to run queries with the deployment hash that is deployed (after the graph build/create command run prior to the graph deploy command above).

Relevant log output

No response

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.
• [X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

[Eduard-Voiculescu]

Version of graph client is way too old. Which was omitting the flag as it doesn't exist.