-
Notifications
You must be signed in to change notification settings - Fork 822
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
script command fails, Function not implemented #2053
Comments
It definitely looks like we aren't getting
|
Thanks for reporting the issue, yes I can confirm signalfd is not implemented. @therealkenc, is there a post on the strace ENOSYS issue? Just started a thread with folks internally and we will take a look. |
@stehufntdev - No issue ticket specific to the |
Note that this also, for some reason, messes up the terminal after it failed. I'm on 15063. When I run
And afterwards, the terminal doesn't echo stdin anymore (but accept it, e.g. Strace attached. |
Right now, can't use 'bs-loader' on WSL, main webpack module loader for bucklescript/reason, because of this. Instead of working around upstream everywhere that is using script, would be nice having it fixed instead. This is breaking everything that relies on 'script'. @jackchammons @benhillis Is it going to be fixed? |
Dupe of #129 to keep unimplemented |
Your Windows build number: (Type
ver
at a Windows Command Prompt)Microsoft Windows [Version 10.0.15063]
What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
script "echo foo"
What's wrong / what should be happening instead:
Observed: Crashes with
script: cannot set signal handler: Function not implemented
Expected: It should work and not crash.
<cmd>
is failing, then runstrace -o strace.txt -ff <cmd>
, and post the strace.txt output here)Relevant strace:
See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: