Skip to content

Commit 2b027d9

Browse files
sunfishcodesunfishcode
authored
Add an agenda for the 04-09 meeting and the notes for 03-26. (#253)
1 parent 54a8be9 commit 2b027d9

File tree

3 files changed

+110
-0
lines changed

3 files changed

+110
-0
lines changed

‎meetings/2020/WASI-03-26.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,3 +50,77 @@ Installation is required, see the calendar invite.
5050
1. [Proxy-Wasm](https://github.com/proxy-wasm) update.
5151

5252
## Meeting Notes
53+
54+
Attendees:
55+
56+
Dan Gohman
57+
Jan Falkin
58+
Lee Campbell
59+
Till Schneidereit
60+
Alex Crichton
61+
Andrew Brown
62+
Mingqiu Sun
63+
Olaf Tomalka
64+
Piotr Sikora
65+
Pat Hickey
66+
Peter Huene
67+
Sam Clegg
68+
Johnnie Birch
69+
Wouter van Oortmerssen
70+
Luke Wagner
71+
Aaron Turner
72+
Benjamin Brittain
73+
Taylor Thomas
74+
John Plevyak
75+
Ralph Squillace
76+
Brian Hardock
77+
78+
Meeting notes:
79+
80+
WASI currently uses a POSIX-like errno enum, but that seems not well suited for less POSIX-like APIs: https://github.com/WebAssembly/WASI-crypto/pull/13#issuecomment-599324384 Many systems have evolved to having a single error enum shared across the whole system. Is it ok if we don't aim for that?
81+
Lee: we need standardized ways to propagate errors throughout the system which is generic over all kinds of APIs
82+
PH: Design a way to structure and compose errors. We should do this with types, rather than integer ranges.
83+
SBC: Capability system is one of the unifying parts of WASI, there will be errors common to all capability operations.
84+
PCH: Compositional errors might be something like a sum type of different errors.
85+
Bwb: Strings as errors have lots of awkward problems, including internationalization.
86+
PCH: Being able to use any type gives us the power to describe errors.
87+
Jplev: Have a generic error codes, with ways to map to them.
88+
Sbc: Don’t redeclare the same errors as POSIX
89+
Pat: APIs define the things they need now, and we’ll work on factoring things out and composition as we go forward.
90+
Lee: POSIX is a C API and we can map WASI errors to POSIX errno as needed.
91+
92+
93+
POSIX tries hard not to let syscalls cause segfaults, returning things like EFAULT instead. There may be some value in this for POSIX compatibility, but how valuable is this otherwise? Should other WASI APIs be allowed to trap?
94+
Sbc: one of our objectives is to be able to implement WASI as wasm modules.
95+
Lee, sbc: We seem to need core language support for catching traps to really figure this out.
96+
Evolving idea: wasi-sdk API for extra emulation:
97+
```
98+
-D_WASILIBC_EMULATED_MMAN
99+
-D_WASILIBC_EMULATED_PAUSE
100+
-D_WASILIBC_EMULATED_RAISE
101+
...
102+
-D_WASILIBC_EMULATED_ALL ? and
103+
-lwasi-emulated-mman
104+
-lwasi-emulated-pause
105+
-lwasi-emulated-raise
106+
...
107+
-lwasi-emulated-all ?
108+
```
109+
Lee: Do we need the `-l`s? We can just put everythgin in libc.a and it’ll only get linked in
110+
Proxy-Wasm update.
111+
This is an update from the previous presentation in October.
112+
Consolidated many callbacks from the previous presentationtation.
113+
114+
Sbc: Have you looked at creating a witx description?
115+
Piotr: Not yet; we’re still iterating on the API.
116+
Sbc: Do proxy implementations need to implement all callbacks, or are some of the m optional?
117+
Piotr: Some are optional. If you’re only implementing HTTP, you only need to impelment HTTP callbacks.
118+
PH: This proposal is great, and also very big, can we factor out pieces that can be used in other contexts?
119+
120+
Adapting the core CG Phases for WASI.
121+
https://github.com/WebAssembly/proposals/
122+
“Two or more Web VMs”
123+
124+
Reference interpreter, formal semantics
125+
126+
Fitting the existing phases into the process

‎meetings/2020/WASI-04-09.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
![WASI logo](/WASI.png)
2+
3+
## Agenda for the April 9 video call of WASI Subgroup
4+
5+
- **Where**: zoom.us
6+
- **When**: April 9, 16:00-17:00 UTC
7+
- **Location**: *link on calendar invite*
8+
- **Contact**:
9+
- Name: Dan Gohman
10+
- Email: [email protected]
11+
12+
### Registration
13+
14+
None required if you've attended before. Email Dan Gohman to sign up if it's
15+
your first time. The meeting is open to CG members only.
16+
17+
## Logistics
18+
19+
The meeting will be on a zoom.us video conference.
20+
Installation is required, see the calendar invite.
21+
22+
## Agenda items
23+
24+
1. Opening, welcome and roll call
25+
1. Please help add your name to the meeting notes.
26+
1. Please help take notes.
27+
1. Thanks!
28+
1. Proposals and discussions
29+
1. Moving to a CG-style phases process:
30+
https://github.com/WebAssembly/WASI/pull/252
31+
32+
## Meeting Notes

‎meetings/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,11 @@ Meetings of the WASI Subgroup of the W3C WebAssembly Community Group (CG) follow
2323
* [WASI November 21st video call](2019/WASI-11-21.md)
2424
* [WASI December 5th video call](2019/WASI-12-05.md)
2525
* [WASI December 19th video call](2019/WASI-12-19.md)
26+
27+
### 2020
28+
2629
* [WASI January 16th video call](2020/WASI-01-16.md)
2730
* [WASI February 27th video call](2020/WASI-02-27.md)
2831
* [WASI March 12th video call](2020/WASI-03-12.md)
2932
* [WASI March 26th video call](2020/WASI-03-26.md)
33+
* [WASI April 9th video call](2020/WASI-04-09.md)

0 commit comments

Comments
 (0)