Closed chr7 closed 3 years ago
I think this is relatively harmless. As you say the app continues running (something should be catching the raise ServerError
in order to report back to the user). The rest of the stack trace splat could be useful for other causes of such. In this case we can tell it was just companion.orerve.net not responding in time, rather than an actual issue in the code.
This still occurring?
I'm using version 4.2.3 in the meantime and couldn't notice it again.
Describe the bug EDMarketConnector 4.0.4 throws exception: "socket.timeout: The read operation timed out". The exception is thrown in the background, so the app continues running.
Traceback
Desktop (please complete the following information):
Additional context