@dchelimsky Thanks for fixing the reflection warnings on aws-api master. I and a group of people are trying to use the lib with GraalVM native-image and that helps.
Can we use the master version using deps.edn? Is this just a matter of updating com.cognitect.aws/api {:mvn/version "0.8.484"}
to the master SHA?
Yes, that’s how you do it.
cool, thanks
Sounds interesting! Is there discussion somewhere where I could follow?
@valtteri About using it with native-image?
Yea, I’m guessing you’re trying to get it to work with babashka?
@valtteri correct, we're writing a babashka pod
That would be super cool. I’m interested to spectate at least but I can also try to help if I can. My gh username is vharmain
OK, I'll add you
Thanks a lot!
@dchelimsky I'm looking at a reflection warning in the cognitect.http-client code, but I have trouble finding where that is hosted on github. Is that generated code perhaps?
it's around line 108 in the cognitect.http-client namespace:
"Class java.nio.HeapByteBuffer[] is instantiated reflectively but was never registered. Register the class by using org.graalvm.nativeimage.hosted.RuntimeReflection"
Can also fix this using a config
The code is open source (it’s in the jar), but the repo is not public.
right
yeah, I already found the source using (slurp (io/resource ...))
:)
How can you fix it with a config?
In GraalVM native-image you can pass it a config with classes that need reflection: Mine now looks like:
[
{"name": "[Ljava.nio.HeapByteBuffer;"}
]
to fix the issue with the http-clientPreferably you fix the reflection issue, but if you really can't this is a way to deal with it
I don’t own that repo, but I know the people who do 😉
I meant "you" in the general sense :)
when dealing with native-image
I’ve reported it, but I don’t anticipate hearing anything back before tomorrow. I’ll follow up here when I know something.
cool, thanks a lot