search

SeattleTestbed / repy_v1

Seattle Testbed's original Repy version 1 sandbox
MIT License
1 stars 4 forks source link

Repy uncaught exception #101

Closed choksi81 closed 10 years ago

choksi81 commented 10 years ago

Failed to read the specified file: 'p2p.repy'

Uncaught exception! Following is a full traceback, and a user traceback. The user traceback excludes non-user modules. The most recent call is displayed last.

Full debugging traceback: "repy.py", line 409, in "repy.py", line 157, in main

User traceback:

Exception (with type 'exceptions.IOError'): 4 Interrupted system call: 'p2p.repy'

*note I ran it again without changing anything(no recompile), it works. I think this is the bug we saw at your office long time ago.

choksi81 commented 10 years ago

Author: hys235 Replying to hys235:

Failed to read the specified file: 'p2p.repy'

Uncaught exception! Following is a full traceback, and a user traceback. The user traceback excludes non-user modules. The most recent call is displayed last.

Full debugging traceback: "repy.py", line 409, in "repy.py", line 157, in main

User traceback:

Exception (with type 'exceptions.IOError'): 4 Interrupted system call: 'p2p.repy'

choksi81 commented 10 years ago

Author: justinc Fixed in r3486.

So this is because a large read may be interrupted by signals (such as those that may happen when a child process exits). These sort of signals happen all of the time on Repy.

I've looked through the code base and the places where we do reads seem to either be small files (like /proc/uptime and /proc/PID/stat) or do line based reads, as is the case for the restrictions file.

I believe the listed line is the only place where this error is likely to happen.

Unfortunately, I can't recreate the error on demand, so I can't make a test that demonstrates the problem. Please reopen the ticket if this doesn't fix the issue.