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 you're in aws lamdba, the lambda can kill the event loop before we manage to send all events.
This means that things complete, but we're missing data for a few nodes/functions.
Steps to replicate behavior
This is hard to recreate locally unless you kill the process immediately after the driver finished executing.
run async driver logging to tracker
immediate kill process
Library & System Information
latest
Expected behavior
The tracker should be able to register something with python to say "hey run this before the process closes" to ensure the events get sent -- we do this with registering stop() with the sync client.
Additional context
Asyncio and atexit don't seem to play well together. There seems to be a library that could help. But yeah could be easy, or could be digging into the internals of python to figure this out.
The text was updated successfully, but these errors were encountered:
Current behavior
If you're in aws lamdba, the lambda can kill the event loop before we manage to send all events.
This means that things complete, but we're missing data for a few nodes/functions.
Steps to replicate behavior
This is hard to recreate locally unless you kill the process immediately after the driver finished executing.
Library & System Information
latest
Expected behavior
The tracker should be able to register something with python to say "hey run this before the process closes" to ensure the events get sent -- we do this with registering
stop()
with the sync client.Additional context
Asyncio and atexit don't seem to play well together. There seems to be a library that could help. But yeah could be easy, or could be digging into the internals of python to figure this out.
The text was updated successfully, but these errors were encountered: