Getting back to rep, and I no longer need patched nrepl.transport and tools.cli to get it to build!! Hurrah!

might as well try with an unpatched clojure

locking macro patch still needed

has anybody been able to use clojure.test\run-tests under graalvm? I've got a small sample working under clojure 1.9 but I am getting the unbalanced monitors error when trying to create a native-image when using clojure 1.10. @eraserhd, maybe I need the patch you are using? By locking macro patch, do you mean CLJ-1472-reentrant-finally2.patch from https://clojure.atlassian.net/browse/CLJ-1472 ?

that issue is a bit of a pain in the ass. what I have done for some projects is patch or just copy the clojure code and remove any references to locking

you might also use this workaround: https://github.com/taylorwood/clojurl/commit/12b96b5e9a722b372f153436b1f6827709d0f2ab it introduces a special form for locking and then uses that special form to patch several clojure functions.

thanks @borkdude! I'll start with the taylorwood work-around.

that man rocks

shoutout to @taylor

lread: That error is definitely what I get without the locking patch.

ok, thanks @eraserhd, another avenue to explore.

I wonder what is different about clojure 1.9 and clojure 1.10 that this error started happening so often. maybe clojure 1.10 loads spec while doing things like resolve?

The reentrant-finally2 patch is trying to fix the bytecode generation, hmm.

I was using the clj-1472-2.patch, which punts it to Java.

hmm... thanks there is also a clj-1472-3.patch

er, that's probably the one

it is a bit confusing, the JIRA issue references the clj-1472-3.patch but CLJ-1472-reentrant-finally2.patch was created later.

@borkdude, I was hopeful when I saw -Dclojure.spec.skip-macros=true in your clj-kondo compile script. I thought it might be related to this issue.

that was one attempt to deal with this issue

and maybe also some speedup, but not sure what the effect was

ah ya maybe, see it recommend for cli-matic for startup time: https://github.com/l3nz/cli-matic#reducing-startup-time-with-skip-macros

@lee thanks for sharing that tip

while wandering lost in the woods, I see many interesting things.

@borkdude have you started notarizing+stapling your GraalVM binaries yet? thinking to start solving this problem and want to collect some info. 🙂

i'm using https://github.com/mitchellh/gon on other stuff right now but want to make something just aliasable in deps.edn for it.

@gerred I haven't looked into this. Will users get into trouble with my binaries if I don't?

wow, draconian

apple's thing that is

https://github.com/mitchellh/gon#prerequisite-acquiring-a-developer-id-certificate

i wonder if that impacts atom plugins and vscode extensions

i guess this is getting off-topic

@borkdude a link from the gon page shows what users may have to do: https://github.com/hashicorp/terraform/issues/23033#issuecomment-542302933

not off-topic as far as I'm concerned: this affects all graalvm built clojure binaries

the description looks like what i went through recently

i wouldn't have classified it as painful -- but then development-type folks are used to having to do these kinds of "extra" things

the binaries I produce are generally for developers, so I guess it's fine

definitely not convenient though

I'll make an issue for it

and look into it later. I'm not running catalina myself yet

do you have to pay Apple for a developer account/certificate?

maybe there can be a brew tool that whitelists all kinds of binaries, like a .catalina_ignore or something

not sure about the dev cert -- if you happen to fit in this category, then no you don't have to pay? https://developer.apple.com/support/membership-fee-waiver/

or maybe brew can sign these things 🙂

perhaps

Fee waivers are not available for: Individuals and sole proprietors/single person businesses

there is some discussion starting here: https://discourse.brew.sh/t/all-binaries-must-be-signed-in-future-macos/4963

this doesn't affect homebrew/downloading from the terminal

it does affect binaries downloaded via browsers and apps though.

hmm...i think i did have to do something to get clj-kondo to work...am i confusing some issues?

maybe you downloaded it from github?

but if you install it from curl it will work?

unfortunately, i'm weeks away from the env where i tested it

likely there's someone else around who can verify

> this doesn't affect homebrew/downloading from the terminal what about binaries you install with homebrew, but are then executing using some other App like http://Emacs.app?

anyway @gerred if you create a tool for it, I'm willing to try it

it's just that 99 euro a year that apple wants from me, while I'm giving my tools away for free, which feels a bit wrong

that'll be ok ^ the quarantine flag is a bit that gets set on the binary

yeah

maybe Clojurists Together could invest in a Developer ID cert and come up with a process for that? I'd be willing to develop some tooling there to enable that for binaries.

it's insane though.

i guess this kind of thing tends to happen when there's a fair bit of $$$ on the line

@danielcompton 👋