Sebastian Hoß

https://github.com/stefanbirkner/system-lambda might be an option as well

You can declare the nrepl dependency in scope "test" and "provided". It will still be picked up by the clojure:nrepl goal, but doesn't pollute downstream. See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html for reference.

I have some error & workaround to share. The error message looks like this: ```shell !!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!! Terraform crashed! This is always indicative of a bug within Terraform....

@apparentlymart ok created https://github.com/hashicorp/terraform/issues/32092 for that @bflad yeah I understand. I was aware of this ticket here before deciding to give it a try and was actually surprised how well...

+1 for the PathSubject. Currently the following does not compile due to method ambiguity: ``` @Test public void shouldConvertToPath() throws IOException { // given final Path expectedPath = ...; //...

No problem! More importantly, the tests failure looks like a flaky github actions behavior? It seems that the cluster creation in the step before timed out and thus there were...

Solved the merge conflicts

Yeah that works and its my current workaround, however I would still prefer to just use the `variables` section as a nice-to-have feature. That said, I have checked other tools...

AFAIK these `$patch` directives are just part of [strategic merge patches](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md) and their usage is explained [here](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md#basic-patch-format). That said, that document is deprecated & it would be really cool to...

oh yeah you are right - that must be https://github.com/kubernetes/kubernetes/pull/113245 which was introduced in 1.28