Page MenuHomePhabricator

Pull logs should let us identify client disconnects
Open, NormalPublic


We just saw an issue where a user was having difficulty fetching and pushing over a wired connection, but could perform operations without issue on a different (wireless) connection. This points strongly at router ghosts or haunted ethernet cables.

The pull logs aren't currently robust enough to identify when an error follows a client disconnect. If we recorded situations were we observed a client disconnect followed by the underlying process exiting, we'd have a clearer picture about when issues are on the client side vs our fault.

Related Objects