Node.js uvwasi team Meeting 2023-03-15

[mhdawson]

Time

UTC Wed 15-Mar-2023 18:00 (06:00 PM):

Timezone	Date/Time
US / Pacific	Wed 15-Mar-2023 11:00 (11:00 AM)
US / Mountain	Wed 15-Mar-2023 12:00 (12:00 PM)
US / Central	Wed 15-Mar-2023 13:00 (01:00 PM)
US / Eastern	Wed 15-Mar-2023 14:00 (02:00 PM)
EU / Western	Wed 15-Mar-2023 18:00 (06:00 PM)
EU / Central	Wed 15-Mar-2023 19:00 (07:00 PM)
EU / Eastern	Wed 15-Mar-2023 20:00 (08:00 PM)
Moscow	Wed 15-Mar-2023 21:00 (09:00 PM)
Chennai	Wed 15-Mar-2023 23:30 (11:30 PM)
Hangzhou	Thu 16-Mar-2023 02:00 (02:00 AM)
Tokyo	Thu 16-Mar-2023 03:00 (03:00 AM)
Sydney	Thu 16-Mar-2023 05:00 (05:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+uvwasi%20team+Meeting+2023-03-15&iso=20230315T1800
• or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+Mar+15%2C+2023+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1lZ64O_yOO19W9EUxhmU9bEF6qiN3C5JAkrB5VpznUvk/edit

Agenda

Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/uvwasi

• uvwasi team working tasks #187

Invited

• uvwasi team: @nodejs/wasi

Observers/Guests

Notes

The agenda comes from issues labelled with uvwasi-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

• link for participants: https://zoom.us/j/91612484369
• For those who just want to watch:
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[tniessen]

I might only be able to attend for a part of the meeting, but I'll try to make it.

[mhdawson]

Minutes from the meeting today:

Node.js uvwasi team Meeting 2023-03-15

Links

• Recording: https://www.youtube.com/watch?v=TBfAsOq7R0w
• GitHub Issue: Node.js uvwasi team Meeting 2023-03-15 #193

Present

• Michael Dawson (@mhdawson)
• Blaine Bublitz (@phated)
• Andrew Brown (@abrown)
• Oscar Spencer (@ospencer)
• Guy Bedford (@guybedford)
• Pat Hickey (@pchickey)
• Tobias Nießen (@tniessen)

Agenda

Announcements

*Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/uvwasi

• uvwasi team working tasks #187
  • Walked the the items/progress on them
  • Guy - some work in https://github.com/bytecodealliance/jco on experimenting on how to implement. Good starting point to understand what preview 2 workflows/apis might look like. Working on trying to figure it out while it is all changing. Things might possibly work
  • Finding more people to contribute
    • Andrew looking for issue list:
      • Oscar - TLDR;
        • Get everything in snapshot 1 implemented, biggest gap is socket support
      • Michael - Add documentation #14 is another good one.
  • Andrew how do I know if implementation is consistent with other implementations
  • Pat, there is work on a conformance suite
    • https://github.com/WebAssembly/wasi-testsuite/
  • Andrew
    • Have some suggestions on the wasi-testsuite repo, once those are resolved will look into
      adding testing/running it on uvwasi
  • Andrew
  • WASI threads, WASI crypto are two that I’ve been interested in
  • Know that Node.js already has crypto APIs, if you added would it be through uvwasi or
    through existing crypto APIs in Node.js
  • Oscar you could do both, but from the uvwasi perspective would be better in uvwasi itself
    so that it can be shared across users.
  • Tobias, we might want to first experiment in JavaScript. Some tools like electron use
    something other than OpenSSL.
  • Michael how complex is the WASI crypto?
  • Pat, quite complex, but low uptake,
  • Blaine, uvwasi, adding a bunch of crypto does not make a lot of sense just based on the name
  • Blain, key issue is how we specify loading of worlds, versus deciding what worlds can be supported. Ideally native addons could also provide worlds
    • Andrew could wit-bindgen help? Ideally once I specify my WIT interface I would like my implementation code to be easily "usable" in Node.
    • Guy would be good to figure out that pattern work together on that
    • Guy, no roadblocks to stability, but we should figure out.
    • Guy will open issue in uvwasi, to start discussion of what API may look like with worlds
  • Tobias
    • Great thing is that it lets you do things mostly on 1 thread
    • Today uvwasi is synchronous, so need to use different threads
    • V8 recently added feature to allow WASI implementations to return promises: https://v8.dev/blog/jspi
    • Blaine, don’t think wasi snapshot 2 is looking at async at all
    • Blaine does it break the WASM sandbox model
    • Blaine, dependence on v8 webassebly only thing, therefore would not want in uvwasi itself, but might make sense in Node.js else.

Q&A, Other

Upcoming Meetings

• Node.js Project Calendar: https://nodejs.org/calendar

Click +GoogleCalendar at the bottom right to add to your own Google calendar.