You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the call .add_event() fails due to the connectivity issues to your servers or some other reason, it will throw an exception that will kill the thread that called it.
This is something you want to avoid for a tracking library - I want my services to still work even if your servers are down or unreachable to some other reason.
Now, I have to rely on using a ThreadPoolExecutor with try ... except that catches all exceptions and does logging.
The text was updated successfully, but these errors were encountered:
It sounds like half of the problem is Issue #9 and the other half is due to holes in error handling. Correct? So initially the latter is going to be easier to correct as a mitigation, but Issue #9 will still need to be addressed.
If the call .add_event() fails due to the connectivity issues to your servers or some other reason, it will throw an exception that will kill the thread that called it.
This is something you want to avoid for a tracking library - I want my services to still work even if your servers are down or unreachable to some other reason.
Now, I have to rely on using a ThreadPoolExecutor with try ... except that catches all exceptions and does logging.
The text was updated successfully, but these errors were encountered: