-
Notifications
You must be signed in to change notification settings - Fork 161
Closed as not planned
Closed as not planned
Copy link
Labels
internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)rejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable futuretestsPRs that add or change testsPRs that add or change tests
Description
Summary
Over the past few days the integration tests for the Idempotency utility have been failing consistency on test cases that assert the behavior of the Idempotency utility in the event of Lambda timeouts.
The implementation of the utility hasn't changed so we should investigate why this is happening and if needed provide a fix.
Why is this needed?
So that we can continue running integration tests on the utility and maintain a level of confidence that it works on Lambda.
Which area does this relate to?
Tests
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)rejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable futuretestsPRs that add or change testsPRs that add or change tests
Type
Projects
Status
Closed