@poppgs I just answered, apologies for the delay. Tl;dr it should be largely harmless, and it's a bug that we've seen internally, but it just means that the extension socket is gone before your extension can connect. The problem I believe is that in osquery-Python doesn't check the existence of the socket before attempting to connect