This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-18
Channels
- # announcements (1)
- # babashka (39)
- # babashka-sci-dev (59)
- # beginners (60)
- # calva (14)
- # circleci (1)
- # clj-kondo (16)
- # clj-on-windows (1)
- # clojure (95)
- # clojure-europe (5)
- # clojure-norway (2)
- # clojurescript (34)
- # conjure (2)
- # core-async (55)
- # datomic (4)
- # emacs (54)
- # holy-lambda (5)
- # hyperfiddle (2)
- # interop (4)
- # lsp (8)
- # malli (3)
- # nrepl (4)
- # off-topic (34)
- # polylith (5)
- # reitit (3)
- # releases (2)
- # shadow-cljs (85)
- # specter (2)
- # testing (8)
- # tools-deps (12)
Hi, I am new to holy-lambda/graalvm and got a basic hello-world native lambda working. Now I have added aws-api with dynamodb to it and during the bb hl:native:executable phase, I get the following error:
Error: Classes that should be initialized at run time got initialized during image building:
jdk.xml.internal.SecuritySupport was unintentionally initialized at build time. To see why jdk.xml.internal.SecuritySupport got initialized use --trace-class-initialization=jdk.xml.internal.SecuritySupportJust add this class to —initialize-at-build-time. For GraalVM issues it’s easier to get help on #graalvm channel.
The rule of thumb is whenever you see this error just add the class listen in the error to —initialize-at-build-time. See: https://github.com/FieryCod/holy-lambda/tree/master/examples/bb/native/cognitect.aws.api bb.edn file :native-image-args.
Awesome, that works! I was flipping between that document and this https://fierycod.github.io/holy-lambda/#/native-backend and missed overlooked step #7