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.
refs: #10574
Description
This pull request aims to facilitate the observation of the behavior described in issue #10574 where the readFully method from the Agoric client-utils package fails when attempting to read a vstorage node.
To achieve this goal, the following changes have been made:
packages/client-utils/src/vstorage.js
have been uncommented to provide additional debugging insights during execution.These changes are intended solely to help identify and understand the root cause of the issue, not to provide a final solution.
Error analysis
The error arises during the readFully method's execution, as observed in the log output. When invoked, the method follows this sequence:
Initial Behavior:
The readAt method successfully retrieves data for the latestQuestion node at the highest block height (439) and appends it to the parts list. Subsequently, the method performs the same operation for block height 367, adding the respective node data to the list.
Error Occurrence:
During the next iteration of the while loop, the readStorage function throws an error. This failure is signaled by the response code of 38.