Clojurians Log v2

@borkdude is there a way to repro the http-client reflection warning on the JVM? I am happy to fix it but don't see a warning when loading the namespace (from Java 11).

@stuarthalloway After closer inspection, I think the warning came from using import java.lang.reflect.Array;. This is the warning I got from graalvm:

"Class java.nio.HeapByteBuffer[] is instantiated reflectively but was never registered. Register the class by using org.graalvm.nativeimage.hosted.RuntimeReflection"

[
  {"name": "[Ljava.nio.HeapByteBuffer;"}
]

@borkdude Thanks for all you are doing exploring that is possible with GraalVM. I don't use it for day job stuff (yet?), but if there is low hanging fruit happy to help grab it.

Good to hear. For context, we are working on a babashka aws pod (which wraps aws-api), which runs natively, so you can use aws-api in scripts without a JVM with very fast startup time.

Babashka pods are basically CLIs but they expose their data through EDN or Transit (or JSON) and can be called using normal functions instead of shelling out, RPC-style.

that sounds terrific

This is a list of existing pods that can already be used from babashka: https://github.com/babashka/pod-registry A few of them are written in Clojure and compiled with GraalVM native-image.

Any idea how to pass x-aws-acl header in the PutObject when using cognitect-labs/aws-api? - I tried overriding the default multimethod for modify-http-request but no luck so far. It's relevant when uploading files so s3 and making them publicly accessible in one request

Which AWS service(s) are you planning on exposing?

Which s3 API?

all that are available in aws-api

we have a working prototype, but there is some stuff around aws-api returning an inputstream for resources from s3 (and possibly others) which we have to translate into bytes, because it has to go over the wire via transit

it seems that aws-api turns a byte buffer into an inputstream for some reason

Ah, forgot to mention - :PutObject

You can (should?) use :PutObjectAcl for this instead of messing with headers.

I see you want to do it in one request, but that’s not how it’s designed.

is the ACL not available on PutObject? (aws/doc client :PutObject)

@lukaszkorecki it’s x-amz-acl, not x-aws-acl. Did your attempt with modify-http-request use the right header name?

you should not need to mess with with modify-http-request for this

pass :ACL

@lukaszkorecki

> is the ACL not available on PutObject? No, @ghadi, it is not not available on PutObject.

FYI :ACL is also available on :CreateBucket

Apparently, my joke about “not not” was missed by at least one reader, so to clarify …. :ACL is absolutely, definitely, 100% a supported key on :PutObject

Got that @lukaszkorecki?

I'll double check in ~45m, AFK right now. But thanks for the pointers - I'm fairy sure there were no typos, but I'll verify everything :thumbsup:

OK. I’d recommend you don’t worry about the header and just use the :ACL key in the :request map. Let us know how it goes!

@dchelimsky that works, thank you! Next time, I'll check aws.client.api/doc

as the ACL param is listed there, of course 🤦

Glad that worked out.