InactiveRpcError
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 361
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
When I use rpc request to get the block id as 22291692, I get the following error message
accessNodes: access-001.mainnet15.nodes.onflow.org:9000
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.NOT_FOUND
details = "not found: failed to retrieve block ID for height 22291692: could not retrieve resource: key not found"
debug_error_string = "{"created":"@1645164230.398433674","description":"Error received from peer ipv4:35.226.94.138:9000","file":"src/core/lib/surface/call.cc","file_line":1074,"grpc_message":"not found: failed to retrieve block ID for height 22291692: could not retrieve resource: key not found","grpc_status":5}"
But I request the latest block, using the current accessNodes(access.mainnet.nodes.onflow.org:9000) can successfully return data
I'm a flow novice, am I doing something wrong?
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 the request for block height 22291692 against access-001.mainnet15.nodes.onflow.org:9000, then compare it with the latest-block request against access.mainnet.nodes.onflow.org:9000. Trace the accessNodes RPC entry point and determine whether the historical height should be available; done means either correcting the request or documenting the service-side cause and expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- blockchain, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100