Fix (benign) socket closed error message
borkdude opened this issue · comments
With this repo, when you repeatedly execute bb bar, then you see a socket closed exception being printed, which is probably benign, but we should fix this.
What's a recommended fix? A more graceful failure message?
@lispyclouds Before fixing we should first diagnose the problem, but I expect that we try to read from a closed socket, perhaps after the pod has already been shut down.