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: implement wasm engine #143

Merged
merged 12 commits into from
Sep 18, 2024
Merged

chore: implement wasm engine #143

merged 12 commits into from
Sep 18, 2024

Conversation

nunogois
Copy link
Member

@nunogois nunogois commented Sep 6, 2024

https://linear.app/unleash/issue/2-2640/create-a-wasm-layer-that-has-feature-parity-with-our-ffi-layer

Implements the WASM engine, using the FFI layer as reference. Updates the tests accordingly.

I opted to use a Response object, like we do in the FFI layer. This should provide us with a very consistent behavior, whether you use the FFI layer or the WASM engine. We can then parse these Response objects in our wrapper and handle them accordingly.

All our client spec tests are currently passing: https://github.com/Unleash/yggdrasil/actions/runs/10888640435/job/30213559806?pr=143#step:9:225

image

@nunogois nunogois marked this pull request as ready for review September 16, 2024 17:02
Copy link
Member

@chriswk chriswk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really cool to me, but I'd wait for @sighphyre

Copy link
Member

@sighphyre sighphyre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, nice work! LGTM

@nunogois nunogois merged commit db3203c into main Sep 18, 2024
3 checks passed
@nunogois nunogois deleted the chore-implement-wasm-engine branch September 18, 2024 10:18
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.

3 participants