python-wasm
python-wasm copied to clipboard
Known Emscripten issue to report upstream
A ticket to collect issues and bugs with Emscripten. We want to report them upstream eventually.
- [x] Emscripten defines
IPPROTO_SCTP, butsocket(AF_INET, SOCK_STREAM, IPPROTO_SCTP)causes an abort, https://github.com/emscripten-core/emscripten/pull/16479 - [x]
clock_nanosleep(CLOCK_MONOTONIC, TIMER_ABSTIME, &timeout_abs, NULL)does not work as expected, causestime.sleepto hang forever.nanosleep(&timeout_ts, NULL)works. https://github.com/emscripten-core/emscripten/issues/16453 - [X]
freeaddrinfocrash https://github.com/emscripten-core/emscripten/issues/16081 - [X]
strftimemishandles quoted percent, https://github.com/emscripten-core/emscripten/issues/16155 - [x] week number of
strftime("%U")and%Wwrong https://github.com/emscripten-core/emscripten/issues/16156 - [ ]
mkfifo()andmknod()create regular file https://github.com/emscripten-core/emscripten/issues/16158 - [x]
opendir/open(O_DIRECTORY)leaks file directory https://github.com/emscripten-core/emscripten/issues/16452 - [X] msync() on anonymous mapping fails, https://github.com/emscripten-core/emscripten/issues/16350
- [ ]
fstatdoes not work on pipes, https://github.com/emscripten-core/emscripten/issues/16414 and https://github.com/python/cpython/pull/31770 - [ ]
fstatdoes not work on unlinked file - [x] Blocking socket
accept()fails withTypeError: Cannot read property 'stream' of undefined, https://github.com/emscripten-core/emscripten/issues/16047 - [x] utimensat sets wrong atime and mtime, https://github.com/emscripten-core/emscripten/issues/16458
- [ ]
umaskis stubbed - [ ]
selectdoes not support non-NULLexceptfds, crashes with assertion error. CPython workaround https://github.com/python/cpython/pull/31865 - [X] strftime
%Vissue, https://github.com/emscripten-core/emscripten/pull/16494
I'm actually surprised a nanosecond timer works at all considering the spectre mitigations
freeaddrinfocrash https://github.com/emscripten-core/emscripten/issues/16081
strftimemishandles quoted percent, https://github.com/emscripten-core/emscripten/issues/16155
Did the two initial issues get reported upstream? Based on how they already fixed the last two issues Christian reported it seems the Emscripten folks are quick to fix things.
Did the two initial issues get reported upstream? Based on how they already fixed the last two issues Christian reported it seems the Emscripten folks are quick to fix things.
No, I haven't had time to create simple reproducers in C for the two initial bugs.