Fork me on GitHub
#announcements
<
2021-09-24
>
pfeodrippe04:09:38

Released v0.0 of Pitoco. https://github.com/pfeodrippe/pitoco, a OSS library to help you check your endpoint schemas (using spec-provider, Malli and Pathom). See quick video at https://youtu.be/iMcUTygFrfk. Totally inspired by what Akita Software has been doing.

👍 9
❤️ 1
1
1
🤯 1
borkdude09:09:50

Announcing clj-easy/graal-config! https://github.com/clj-easy/graal-config A repo that hosts configurations for Clojure and Java libraries that you can use a dependencies in your native-image builds! Join #clj-easy for more info on this.

👍 12
😻 2
1
delaguardo11:09:48

Thanks! Very clever solution to provide such configuration) btw. there is a github action to provision different versions of graalvm as a part of your workflow - https://github.com/marketplace/actions/setup-graalvm-environment

borkdude11:09:47

Yes, I recommended this to @UJ1339K2B but he told me that this doesn't support setting up a development version.

Karol Wójcik11:09:03

@U04V4KLKC yep. Having dev version of Graal would be much appreciated

Karol Wójcik11:09:10

Does the action allows setting multiple Graal versions? If yes where the action set’s the base directory for each?

borkdude11:09:17

I think the point of this setup action is that it adds one version to the environment, we have a slightly different use case, or we should re-organize things in different jobs

delaguardo11:09:19

I can add dev version today. each version installed in the separate directory following …/GraalVM/%graalvm-version%-%java-version%-%arch%/x64 notation. Also this action expose a set of environment variables: • JAVA_HOME • JAVA_HOME_%graalvm-version%.%java-version%.%arch% • GRAALVM_HOME first and last will be overwritten by the last action run but second will be present for every followup steps

delaguardo11:09:55

so it is possible to provision multiple graalvm versions

borkdude11:09:58

so then you can just do setup-graalvm, execute test, setup-graalvm v2, execute test, etc.

borkdude11:09:17

setting GRAALVM_HOME is excellent because this is what most tools already use

borkdude11:09:40

Perhaps you can make it so that setup-graalvm adds always the latest dev version

borkdude11:09:57

This will also solve the problem for us that our builds will fail when the dev version is removed

delaguardo11:09:14

yes, I’m already working on it while we are speaking )

Karol Wójcik11:09:45

Or we can override GRAALVM_HOME from our test suite :D

borkdude11:09:52

@UJ1339K2B I think we can just make a github matrix and use setup-graalvm

Karol Wójcik11:09:05

Thank you @U04V4KLKC :man-bowing:🙏🙏

delaguardo12:09:29

https://github.com/DeLaGuardo/setup-graalvm/pull/20/checks?check_run_id=3700067176 I manage to add suport for latest nightly build. But it requires slight adjustments in workflow file. 1. graalvm: “nightly” 2. personal-token: ${{ secrets.GITHUB_TOKEN }}

delaguardo12:09:15

right now it exposes the same set of env variables except JAVA_HOME_%version%. Because version is unknown before run I expose “JAVA_HOME_NIGHTLY”

borkdude12:09:33

That's not a problem

delaguardo13:09:04

released as 5.0 version

Ivar Refsdal11:09:56

I'm pleased to announce yoltq, a queue library for Datomic that supports retries, backoff, ordering and more. On-prem only. https://github.com/ivarref/yoltq

👍 10
🎉 3
datomic 5
1
Jeff Evans23:09:33

Announcing the first release of java-case, a tiny utility macro for concisely selecting different forms based on the executing JDK version. https://github.com/jeff303/java-case This is my first Clojure library, so all suggestions/feedback welcomed.

🎉 28
😍 3
seancorfield23:09:20

Nice! I have a use for this at work immediately to replace the ad hoc stuff we're currently doing. And thank you for using clj-new and build-clj!

Jeff Evans00:09:24

Thanks, Sean. Great to hear. And yeah, clj-new definitely made it super easy to publish to Clojars, which was nice.