Skip to content

Exiting STS causes weird behavior #40

@colin-scott

Description

@colin-scott

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions