Leonard Brünings

I tend to agree with @Vampire and I also acknowledge that the documentation is misleading, especially the sentence: > Data providers are queried for their next value only when needed...

Thanks @Vampire, for the detailed answer and for providing a workaround. I agree with your reasoning about not changing anything in Spock.

Possibly related we also experience an issue when running parallel builds on CI ``` Exception is: org.gradle.internal.service.ServiceCreationException: Could not create service of type FileHasher using GradleUserHomeScopeServices.createCachingFileHasher(). at org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:816) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:749)...

While I also want to get rid of this confusing behavior, I think we should postpone it until Spock 3.0, as the breaking change is quite significant.

Maybe the docs in http://spockframework.org/spock/docs/1.1/all_in_one.html#_argument_constraints should be improved to state that it requires a ClosureLiteral and not just an instance of the closure to be treated as a code argument...

Please provide a [SSCCE](http://www.sscce.org) and provide the other info that is suggested in the issue template. This works fine: ```groovy class SuppressedExceptions extends Specification { def "Mock interaction violations don't...

@Vampire, is it possible to get Renovate to update the Kotlin files as well?

If I see it correctly, [typesafegithub](https://github.com/typesafegithub/github-actions-typing-catalog/tree/ae771a97b4318b515803ec388db11fc12c37c46d/typings/actions/checkout) does not even support v6 at the moment.

https://github.com/typesafegithub/github-actions-typing-catalog/issues/123

I'm disinclined to complicate an already really complicated part of Spock, but for the sake of argument I'd be interested in the use case(s) for this @ptomaszek.