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
Last night we had a regression in the new Metrics provider (#2909) and debugging took longer than necessary since Logs faced eventual consistency errors.
Our E2E utils get_lambda_response doesn't fail fast if the invoked function had an error it couldn't handle, since it's synchronous.
Which area does this relate to?
No response
Solution
Add a new option to get_lambda_response to fail fast by default unless required to ignore an error (e.g., testing race conditions, timeouts, etc.).
Why is this needed?
Last night we had a regression in the new Metrics provider (#2909) and debugging took longer than necessary since Logs faced eventual consistency errors.
Our E2E utils
get_lambda_response
doesn't fail fast if the invoked function had an error it couldn't handle, since it's synchronous.Which area does this relate to?
No response
Solution
Add a new option to
get_lambda_response
to fail fast by default unless required to ignore an error (e.g., testing race conditions, timeouts, etc.).Acknowledgment
The text was updated successfully, but these errors were encountered: