Fork me on GitHub
#graalvm
<
2019-11-22
>
lread01:11:14

well, I did not make progress on reducing my RAM footprint for running rewrite-cljc tests, so I took a break a tried http://drone.io cloud. It did quite nicely using 12.5gb of heap for native-image: https://cloud.drone.io/lread/rewrite-cljs-playground/12

👍 1
dharrigan11:11:08

Now that GraalVM has a LTS release, I really really hope that https://clojure.atlassian.net/browse/CLJ-1472 can be fixed/resolved in a new Clojure release.

borkdude11:11:42

It's now the second most popular issue on ask. Please spread the word

dharrigan11:11:08

That gives me a 404

dharrigan11:11:35

Yes, came across that in my travels of click-click clicking links

dharrigan11:11:15

Fingers crossed! Here's hoping!

borkdude11:11:39

@dharrigan There are some open TODOs in the clj-graal-docs regarding CLJ-1472. @alexmiller said: > cleaning all this info up and making a really readable ticket would be really helpful. this is basically what I would do on this ticket (https://clojure.org/dev/creating_tickets) and is a huge boost to getting it ready to screen (Alex in #graalvm) I'm not sure how a community member can clean up an existing ticket though.

andy.fingerhut11:11:52

If someone has exact text they want copied and pasted into a ticket, I should have permission to edit JIRA tickets. That is fine for once-a-week kinds of change frequency, but you should ask Alex Miller for JIRA account (after signing Clojure CA) if you may want to do it more frequently, or long term.

borkdude11:11:21

I do have a JIRA account

borkdude11:11:46

oh, I can just edit that issue? ok... 😛

borkdude11:11:27

so any suggestions/help with those TODOs is appreciated as well