Closed
Description
Two expirations are stored on the DDB table:
- expiration - how long to cache the results of the operation. User-tunable ( seconds since epoch )
- in_progress_expiration - expire records that timed out during lambda execution. Set by powertools to the remainingExecutionTime. ( milliseconds since epoch)
When a request comes in, we try and conditionally upsert the DDB record - if the in_progress_expiration time is before now(), we can overwrite it, else we can't. The bug is here:
We set now once, but we use it in a comparison where the units should be seconds, and another where the units should be milliseconds.
The upshot of this i 660F s that if a handler times out within an idempotent operation, we'll start seeing exceptions thrown for subsequent invocations.
What were you trying to accomplish?
Expected Behavior
Subsequent executions after a function timeout should update the DDB table and complete.
Current Behavior
Possible Solution
- Provide
nowMsandnowin the DDB conditional update - Increase test coverage
Metadata
Metadata
Assignees
Type
Projects
Status
Shipped