Skip to content
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

Exiting STS causes weird behavior #40

Open
colin-scott opened this issue May 12, 2014 · 0 comments
Open

Exiting STS causes weird behavior #40

colin-scott opened this issue May 12, 2014 · 0 comments
Labels

Comments

@colin-scott
Copy link
Member

A common example is that socket objects will randomly become None after SIGTERM has been caught and during cleanup, causing our code to throw null pointers.

I've been putting up if sock=None guards all over the place in the code. This is clearly a stopgap.. should try and figure out what's going on. Could take a long time to figure out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant