Closed stasoid closed 5 years ago
Pyret's client-server compiler has multiple issues with the current sandboxing rules. I'm not sure if there's a way around that.
Can you give some details, so I can report them to language creators? They seem interested in adding Pyret to TIO too. At least I would be able to explain why it can't be added.
It's trying to read an SSL certificate and to connect to a Unix domain socket.
Both may be possible in the future—I'm working on a less restrictive sandbox, but I can't allow access to one cert and one socket without allowing access to all of them...
https://tio.run/#nikud and https://tio.run/#ursala are live. Thanks!
I've unlisted Pyret for now.
Thank you.
I was advised to use
pyret-npm
package for Pyret on TIO.-q
hides compilation messages, I used this in the wrapper. Also,--checks none
can be used to remove "The program didn't define any tests." message, but it is not recommended, so I don't use it. Hello world button is frequently used to start a new program, so I don't use--checks none
for Hello world either.Quoting the answer: