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 namespace to extism:host/env #24

Merged
merged 26 commits into from
Nov 12, 2023
Merged

Conversation

zshipko
Copy link
Contributor

@zshipko zshipko commented Nov 9, 2023

Similar to: extism/extism#511

  • Updates the SDK to be compatible with new namespaces
  • Updates test Wasm to use the new namespaces
  • Some updates to our WASI code for better reactor support. After updating some of the plugins I ran into issues with how the initialization was happening for non-command modules.
  • Uses GET by default if no method is passed to http_request

chrisdickinson and others added 21 commits November 9, 2023 11:44
- 2023-10-20  6:00pm: hey, the tests pass now
- 2023-10-20 11:00pm: hey! we're passing data around
  - tomorrow:
    - implement host->guest and host->worker->guest calls
    - create a wasi
- 2023-10-21 10:40am: stuff all of our internal config into an interface
  - I kind of think we want a `wasi: WASI | boolean` flag instead of `useWasi: boolean`
- 2023-10-21  1:09am: update deps
- 2023-10-22 10:51pm: whew! lots of stuff working now! next up: host functions!
- 2023-10-23  2:51pm: okay, I have to do some more major surgery: callcontext needs to
   		      be instantiated per invocation and live canonically on the host
		      thread
- 2023-10-25 12:40pm: blocks are transferred between the main and background threads
		      as-needed now. what a ride.
- 2023-10-25 11:08pm: all of the tests from the original deno test suite pass now.
- 2023-10-26  9:57am: we lint!
- 2023-10-26 10:26am: all of the examples work!
- 2023-10-26 12:51pm: add DEVELOPING.md, artifacts tests
this tests transferring data from the host back down to the guest thread where
the data exceeds the SAB scratch page length.

there's only one bug thus far: firefox gets caught in a Atomics.compareExchange
loop.
@zshipko zshipko changed the title chore: update default Extism namespace to extism:host/env chore: update Extism namespace to extism:host/env Nov 9, 2023
Copy link
Contributor

@chrisdickinson chrisdickinson left a comment

Choose a reason for hiding this comment

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

Thanks for sorting out the Haskell/WASI init order & updating the namespaces!

I saw one bug – ttp_request instead of http_request – and a formatting thing in the polyfills, but just format should fix that up. Otherwise this LGTM! Once these are fixed feel free to merge at will!

Co-authored-by: Chris Dickinson <chris@dylibso.com>
@nilslice nilslice mentioned this pull request Nov 12, 2023
@nilslice
Copy link
Member

Added #26 to run tests, just case something is weird. just test failed to parse deno.lock on my machine. I probably skipped a step, so I'm just running CI instead 😄

@chrisdickinson
Copy link
Contributor

chrisdickinson commented Nov 12, 2023

@nilslice Ah yeah – you might check your Deno version – v1.36 is the minimum supported version. Thanks for PRing that!

@nilslice
Copy link
Member

@chrisdickinson, indeed I had too old of a Deno installed!

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