Okay, first POC is up and running & feels good 🙂

But test make some problems: If I use normal deps-test the bb-specific namespaces can not be resolved

(ns dda.devops-build.image
  (:require ...
            [babashka.tasks :as t])

https://blog.michielborkent.nl/babashka-test-runner.html

just in time 🙂

I didn't notice your (separate) question since I didn't look past your first question to which I didn't have an answer

https://repo.prod.meissa.de/meissa/dda-devops-build/src/branch/clj-bb-rewrite/bb.edn Works like a charm 🙂 In this case it will make sense to keep only the main paths & deps in deps.edn and the testing-stuff in bb.edn I assume?

yes

thx for your nice help ... and for the cool work :-)

From a native-image I get only:

$ ys -Ye 'ENV.keys()'
- HOME
- USE_NATIVE_IMAGE_JAVA_PLATFORM_MODULE_SYSTEM
- PATH
- PWD
- LANG

I set ENV with:

(sci/intern @ys/sci-ctx 'clojure.core 'ENV (into {} (System/getenv)))

Is that set maybe happening at build time?

no

unless I really don't understand something. It looks like a purposefully minimal env but I just noticed USE_NATIVE_IMAGE_JAVA_PLATFORM_MODULE_SYSTEM

that's probably a key worth googling

If I run the jar in the JVM it works fine

but I think I need to enable something in the native-image build setup

Having trouble finding what

Can you show us where/how you are calling (System/getenv)? Just to rule out build time vs runtime.

sure sec

https://github.com/yaml/yamlscript/blob/main/core/src/yamlscript/runtime.clj#L90

You can repro this with:

git clone [email protected]:yaml/yamlscript
cd yamlscript/
. .profile 
YS -pe ENV
make -C ys build
ys/bin/ys -pe ENV

$ type YS
YS is a function
YS () 
{ 
    ( set -e;
    base=$YAMLSCRIPT_ROOT/ys;
    libyamlscript_version=0.1.39;
    jar=yamlscript.cli-$libyamlscript_version-SNAPSHOT-standalone.jar;
    make --no-print-directory -C "$base" jar;
    java -jar "$base/target/uberjar/$jar" "$@" )
}

I can't easily make sense of or execute the above repro.

You can run those 6 commands verbatim

$ . .profile 
.: no such file or directory: .profile

https://github.com/yaml/yamlscript/blob/main/.profile

cd you not cd into the clone?

ya did

oh. source .profile 😕

zsh?

could be my shell, ya

what shell?

. ./.profile does not return an error

ok cool

Ok, running your YS -pe ENV and that seems to be downloading graalvm!

I already have that installed tho... are you getting me into trouble here?

no

pinky swear?

it downloads graal and lein into /tmp/yamlscript/ and ignores anything else you use

it will work on any system java installed or not

I appreciate you digging. Was hoping this was something @U04V15CAJ knew off the top of his head. I'm writing my YS talk for tomorrow night and no tuits to dig on this 😞

Well, they have suggested the usual cause of confusion above.... build time vs runtime. Oh. Right. You are calling (reset!...) when the namespace loads. So that will happen a build time,ya?

Oh wait my eyeballs didn't work.

that's it

Ok, Loaded in emacs, so I can better see indentation! Ya, System/getenv is called when ns loads.

So build time.

Right:

$ (cd /tmp; ys -pe CWD)
"/home/ingy/src/yaml/yamlscript/ys"

that was supposed to be /tmp

thanks!!!

No prob, sometimes those blind spots just need another set of eyeballs.

I really appreciate you doing this @UE21H2HHD I owe you one!

And thanks too @U013JFLRFS8 I really didn't understand something 🙂

I think I actually had this right before but refactored without the right tests

Things happen. Glad you are sorted out!

$ (cd /tmp && FOO=123 ys -e 'say: "FOO=$(ENV.FOO) cwd=$CWD"')
FOO=123 cwd=/tmp

To see that as Clojure:

$ ys -ce 'say: "FOO=$(ENV.FOO) cwd=$CWD"'
(+++ (say (str "FOO=" (__ ENV 'FOO) " cwd=" CWD)))

the future-call var is copied straight over from core, so I don't see a reason it should work any differently from JVM Clojure