-
Notifications
You must be signed in to change notification settings - Fork 16
feat(bottlecap): handle OOM exceptions #467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
adding trace id and span id so data is not rejected by backend, also added the error
…ion into jordan.gonzalez/bottlecap/timeout-handling
| Event::OutOfMemory => { | ||
| let mut p = invocation_processor.lock().await; | ||
| p.on_out_of_memory_error(); | ||
| drop(p); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this explicit drop?
They are all over the place and I think they are useless since it is done automatically at the end of the block
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe not on the ones where we have it at the end, we can improve this later
What?
Handles OOM exceptions, sending enhanced metric as expected.
Notes
Metrics look iffy, but that's OK, because when the sandbox get's signal-killed, there's no way for us to tell that we got OOM as of now.