-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ntwk/hyperspacenet #1114
Ntwk/hyperspacenet #1114
Conversation
yielded the following errors in
only the block at parent messages of the higher epochs (>2000), exist on the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tldr, vm_messages
task seems to be off by 1, height 1 block possibly due to cbor parsing error (ntwk was reset before 2022/12/16 accdg to patrick from f8)
26d3e0e
to
fe11b3f
Compare
I ran a walk using the fe11b3f commit and the issue still persists.
|
I run a walk job with all tasks once again using commit c48824d --
|
I have updated the branch to the most recent tag from lily. All tasks appearing to be working with the exception of VM messages. The errors @kasteph mentioned above are still occurring. I did a bit of debugging and it appears the messages params failing to parse are indeed invalid params. I am not sure why vmmessage receipts have an |
Fix for VMMessage failures for |
The other VM message failures for |
lotus release with new fix landing shotly: filecoin-project/lotus#10137, we'll need to update to this when it's ready |
I pulled in the version of lotus at the latest ntwk/hyperspace commit into lily and now getting mostly
|
@kasteph the errors around |
Version8 Version = 8 | ||
Version9 Version = 9 | ||
Version10 Version = 10 | ||
Version11 Version = 11 | ||
) | ||
const ( | ||
AccountKey = "account" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will need to add the evm actor key from fip-0054 here?
A couple of FMV/Lout issues still affecting this work:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another RC is coming tomorrow, should we just wait for that?
Yeah, this branch will remain unmerged until lotus cuts a final release. |
- update ffi and lotus hyperspace deps
- generate v10 actor state accessors - update integrated state processor actor version
- there are still some bugs in lotus that prevent lily from running correctly
* feat: implement actor event task and schema - track the value of EventRoots contained in message receipts.
- create a table that records raw message parameters
ab1e2d1
to
bf45275
Compare
- it handles the case of legacy events
4186d9d
to
8ed9fae
Compare
124dc79
to
5086d95
Compare
build this code with
make hyperspacenet
Will merge when lotus cuts v1.20 release and we pull said deps in.