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

Support already completed journals in lambda handlers #189

Merged
merged 1 commit into from
Nov 20, 2023

Conversation

jackkleeman
Copy link
Contributor

Fixes #188

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for quickly creating this PR @jackkleeman. From what I can tell, the change looks good to me.

Looking at the state machine code of the connection and also the LambdaRestateServer, I am wondering whether we couldn't/shouldn't add a few more integration tests for making sure that the state machine works correctly.

@tillrohrmann
Copy link
Contributor

fyi @igalshilman

@jackkleeman jackkleeman merged commit 0dea824 into main Nov 20, 2023
@jackkleeman jackkleeman deleted the lambda-already-completed branch November 20, 2023 17:40
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.

Lambda invocation seems to deadlock if it gets invoked with a journal with an OutputStreamEntry
2 participants