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 AWS Lambda custom runtime #305

Merged
merged 2 commits into from Mar 21, 2020
Merged

Conversation

dainiusjocas
Copy link
Contributor

@dainiusjocas dainiusjocas commented Mar 21, 2020

AWS Lambda doesn't support signal handling, e.g. here. Therefore, in order for babashka to work, it is needed to disable the handling of SIGPIPE.

I propose to introduce an environment variable to alter the default behaviour and disable the handling of SIGPIPE: BABASHKA_DISABLE_PIPE_HANDLER.

An example project that runs babashka script in AWS Lambda https://github.com/dainiusjocas/babashka-lambda.

@borkdude
Copy link
Collaborator

Without the change Lambda fails in a very similar way as is described here oracle/graal#841

@borkdude
Copy link
Collaborator

So far babashka specific env variables starts with BABASHKA_, like BABASHKA_CLASSPATH.
What about BABASHKA_DISABLE_PIPE_HANDLER?

@borkdude borkdude merged commit b14d239 into babashka:master Mar 21, 2020
borkdude pushed a commit that referenced this pull request Apr 17, 2020
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.

None yet

2 participants