fix tryLocateTx for masterchain dest #84
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue was that for masterchain blocks the client still attempted to fetch shards via
get_shards, then substituted a shard from that list while keepingworkchain = -1and the masterchain seqno.As a result,
listBlockTransactionsreceived an invalid block ID (masterchain workchain + shard from a regular workchain + masterchain seqno), and the liteserver returnedLITE_SERVER_UNKNOWN: invalid block id requested.This fix detects masterchain destinations (
workchain == -1) and uses the masterchain shard directly instead of callingget_shards.