Skip to content
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

fix: 🐛 verify that lambda context was found #4

Merged
merged 2 commits into from
Apr 3, 2024

Conversation

jbleduigou
Copy link
Owner

No description provided.

@jbleduigou jbleduigou linked an issue Apr 3, 2024 that may be closed by this pull request
@jbleduigou jbleduigou force-pushed the 3-using-non-aws-context-will-cause-a-panic branch from cc45c1e to f5a807a Compare April 3, 2024 19:49
@jbleduigou jbleduigou changed the title fix: 🧪 add failing test fix: 🐛 verify that lambda context was found Apr 3, 2024
@jbleduigou jbleduigou force-pushed the 3-using-non-aws-context-will-cause-a-panic branch from febeca5 to 991c4e9 Compare April 3, 2024 19:52
@jbleduigou jbleduigou merged commit 901fd50 into main Apr 3, 2024
1 check passed
@jbleduigou jbleduigou deleted the 3-using-non-aws-context-will-cause-a-panic branch April 3, 2024 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using non AWS context will cause a panic
1 participant