-
Notifications
You must be signed in to change notification settings - Fork 354
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
Merge 2.1.2 and 2.1.3 release changes #2204
Conversation
// | ||
// Please note that any changes to this function need to be accompanied by a bump of | ||
// `MODULE_SERIALIZATION_VERSION` to avoid cached modules from using different amounts of gas | ||
// compared to newly compiled ones. |
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.
Nice!
Now I was wondering if/how we can turn this function into something we can hash and add to the caching path. Either by serializing the function (some scripting language) or serialize the op -> cost as a table/map. Could you create a ticket for that as mid or long-term improvement?
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.
I was also wondering if we can test the cache compatibility by having a test with a cache folder with one wasm + module file inside and testing that it can be executed and works as expected (same gas, etc.).
That would probably catch some panics on the wasmer side and if we assert gas, also gas cost changes.
Also added a note to the cost function