Skip to content
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

chore: update extism-runtime.wasm #32

Merged
merged 2 commits into from
Oct 13, 2023
Merged

chore: update extism-runtime.wasm #32

merged 2 commits into from
Oct 13, 2023

Conversation

zshipko
Copy link
Contributor

@zshipko zshipko commented Oct 12, 2023

Updates extism-kernel

@zshipko
Copy link
Contributor Author

zshipko commented Oct 12, 2023

Interesting, I'm not sure why these tests are failing with the updated kernel, but I will try to debug.

@zshipko
Copy link
Contributor Author

zshipko commented Oct 12, 2023

It seems to be this in particular: extism/extism@64fd246#diff-794fada0ab41e6aff2843d93023ded466de0a93207551bbc74772a69c75a075dR276 - if I remove the - 1 then the tests work in Go, but fail in Rust... I'm still not really clear what's going on.

@zshipko
Copy link
Contributor Author

zshipko commented Oct 13, 2023

Fixed in extism/extism#509

zshipko added a commit to extism/extism that referenced this pull request Oct 13, 2023
#509)

`MemoryBlock::next_ptr` used to calculate the offset to the data of the
next block, but it should be returning the start of the `MemoryBlock`
structure in memory. Also updates the tests for this case.

This was discovered when trying to update the kernel in the go-sdk:
extism/go-sdk#32

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: zshipko <zshipko@users.noreply.github.com>
@zshipko zshipko merged commit 307a3b3 into main Oct 13, 2023
@zshipko zshipko deleted the update-kernel-20230812 branch October 13, 2023 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant