Why aren't permissions restored on `die()`? about isolate HOT 6 CLOSED

Generally, die() is called when things go seriously wrong and it is hard to tell if their state is safe enough to let a non-root user touch it. However, "isolate --cleanup" should be always able to remove the mess. If it is not in your case, please tell us the circumstances and we will fix it.

from isolate.

Okay, I understand the problem better, that makes sense. My issue is that die() is called when the binary we try to execv() does not exist. Since other errors that would prevent me from touching those files can happen anyway, I'll just add permission checks when retrieving the data. Thanks :)

from isolate.

I do not understand why you need to perform any permission checks -- isn't it sufficient to check the exit code of isolate?

from isolate.

Not really. I'm using --stdout and --stderr that point to files inside the box and I'd like to get the output even when there's an error.

from isolate.

from isolate.

Yes, that should work, thanks!

from isolate.