-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: update fuel-core v0.13 #563
Conversation
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.
Can you merge in master?
Coverage report
Show new covered files 🐣
Test suite run success543 tests passing in 49 suites. Report generated by 🧪jest coverage report action from 0ffdab9 |
@luizstacio Seems like all blockers for this are gone (the Rust SDK already supports core 0.13). Let me know if you need help with this, you can also check FuelLabs/fuels-rs#657 for some reference. |
Yes I've taken over this PR, I have it down to 6 failing unit tests related to Storage, seems like values have changed so need to see what has to be updated. |
Sweet! As I said, the rust SDK PR I linked above has all the changes needed if you wanna take a peek. |
This PR update fuels-ts to work with fuel-core v0.13.
On this PR, I had to update message handling. The previous implementation led to errors in the message Id calculation, it would be great to get a deeper look from @camsjams. Looking at the specs, it looks like message data should be encoded and decoded in the same way predicateData is.
On the sway side, we have a blocker related to storage persistency, as the latest is not yet compatible with fuel-core v0.13.
Blockers;
FuelLabs/sway#3181
FuelLabs/fuel-core#737