This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-05
Channels
- # asami (13)
- # aws (7)
- # babashka (4)
- # beginners (16)
- # biff (7)
- # cljdoc (10)
- # clojure (32)
- # clojure-europe (27)
- # clojure-nl (14)
- # clojure-norway (7)
- # clojure-uk (3)
- # clojurescript (2)
- # conjure (2)
- # core-async (13)
- # datalevin (4)
- # datomic (3)
- # holy-lambda (7)
- # kaocha (3)
- # lsp (23)
- # off-topic (39)
- # pedestal (10)
- # portal (5)
- # practicalli (2)
- # rdf (10)
- # releases (1)
- # shadow-cljs (66)
- # tools-deps (146)
- # uncomplicate (1)
- # xtdb (10)
Hey All 👋,
I’m working on setting up a babashka-based Lambda.
When I execute the sam local invoke LambdaGenerateTemplate
command locally I get a runtime error like:
:type java.lang.Exception, :message "[holy-lambda]: Handler example.core.LambdaGenerateTemplate not found!
I checked each of the following items and confirmed they appear correctly configured:
* The Lambda resource in my template has a Handler: example.core.LambdaGenerateTemplate
value
* There is a file located at src/example/core.cljc
with a namespace declaration of (ns example.core …)
* Within the core.cljc file there is a function named LambdaGenerateTemplate
* Within the core.cljc file there is an invocation of (h/entrypoint [#'LambdaGenerateTemplate])
I read over the https://fierycod.github.io/holy-lambda/#/babashka-backend-tutorial, but I did not see any missing steps in my config / setup.
Can anyone shed some light on what I’m missing? 🙏Thanks for the quick response Karol! :)
I created a minimal example repo here: https://github.com/SalvatoreTosti/bb-lambda-min-repo-example.
I was able to trigger the Handler example.core.LambdaGenerateTemplate not found!
exception by running the following:
1. Run bb hl:babashka:sync
2. Run sam local invoke LambdaGenerateTemplate
Ok, I see where the problem is. Basically the bb tasks are including the example.core in the classpath, because I'm using this namespace for testing. Please change the name of your namespace and you are good to go! Sorry for the inconvenience. I will patch it soon!
All the best! 🙂