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
When we click ctrl+c we terminate the neva process without handling it. What we probably should do is to close the context to make sure func-runner is gracefully terminated. It's possible to imagine a situation where some component (e.g. http get) opens a connection and never frees it after ctrl+c (or other termination signals from the OS)
Question is, shouldn't user do these kind of things manually? Why e.g. Go doesn't handle resource freeing automatically?
The text was updated successfully, but these errors were encountered:
When we click
ctrl+c
we terminate the neva process without handling it. What we probably should do is to close the context to make sure func-runner is gracefully terminated. It's possible to imagine a situation where some component (e.g. http get) opens a connection and never frees it after ctrl+c (or other termination signals from the OS)Question is, shouldn't user do these kind of things manually? Why e.g. Go doesn't handle resource freeing automatically?
The text was updated successfully, but these errors were encountered: