Stop warning messages appearing on shutdown.
Until I learn to use asyncio properly this hack will do. I may keep it anyway if there are no ill effects.
This commit is contained in:
parent
d3078a77c7
commit
f548432d8e
2 changed files with 4 additions and 4 deletions
6
BUGS
6
BUGS
|
|
@ -6,9 +6,6 @@ Current
|
|||
have the paused status (yellow).
|
||||
- If a job is paused for longer than the timeout period, sometimes it has
|
||||
the timed out status when un-paused.
|
||||
- When shutting down "Exception ignored in:" noise appears. Four messages
|
||||
for every worker running. This started with the move to asyncio for the
|
||||
workers.
|
||||
|
||||
|
||||
Current (tool related)
|
||||
|
|
@ -241,6 +238,9 @@ Fixed
|
|||
my startup script, but passing otherwise.
|
||||
<- sandbox_fs_test.py is totally different now.
|
||||
- The worker processes are left over after vigil stops. (In sandbox or not)
|
||||
- When shutting down "Exception ignored in:" noise appears. Four messages
|
||||
for every worker running. This started with the move to asyncio for the
|
||||
workers.
|
||||
|
||||
|
||||
Won't fix
|
||||
|
|
|
|||
2
vigil
2
vigil
|
|
@ -1017,4 +1017,4 @@ if __name__ == "__main__":
|
|||
with chdir(root_path): # FIX: Don't change directory if possible.
|
||||
loop = asyncio.get_event_loop()
|
||||
main(root_path, loop, worker_count, is_sandboxed, editor_command)
|
||||
loop.close()
|
||||
os._exit(0)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue