Johan Andrén

Try updating to latest Akka Persistence R2DBC (1.1.2) and Akka Projections (1.4.2)

For the record on how this is implemented in the Java SDK the proxy informs the service of `selfHostName` upon discovery so that it knows where to talk to "itself"...

For the record this is an example of the TS hoops needed when doing this manually as currently needed: 

One more aspect is that a user may want to create the client for a component once and re-use it rather than creating it over and over again, I figured...

None of the usual tools on Linux (gdb, ldd) seems to recognize the kalix-codegen-js.bin as a executable although file says: ``` file /srv/homes/johan/code/lightbend/shopping-cart/node_modules/@kalix-io/kalix-scripts/bin/kalix-codegen-js.bin /srv/homes/johan/code/lightbend/shopping-cart/node_modules/@kalix-io/kalix-scripts/bin/kalix-codegen-js.bin: ELF 64-bit LSB shared object, x86-64,...

Hmm, tried to download the binary manually and getting a lot of disconnects from the Lightbend repo, maybe node doesn't handle that well and that's why the file is incomplete:...

It seems `node-fetch` doesn't report when connection closed before delivering all bytes but instead tells us it is "OK"

Didn't figure out a way to detect this, body is a stream so would have to be comparing `response.headers.get('content-length')` with the number of bytes piped through when done writing or...

Related existing issue: https://github.com/lightbend/kalix-jvm-sdk/issues/1077

Also related: https://github.com/akka/akka-http/issues/4150 (but I thought we decided to accept the cost of an additional .async for all the Kalix JVM SDK component streams instead of running them in-line)