I wanted to post in response to this request from Gradle Team on a defect: https://github.com/gradle/gradle/issues/31438#issuecomment-2589897380. I replied with some details about how to reproduce the problem, and a gradle plugin I created that is experiencing the issue reliably after upgrading to gradle 8.10.2. This details are in this post on github: https://github.com/gradle/gradle/issues/31438#issuecomment-2664493253

And the intention of your post here in this user community is, ... what?

It was a request from asodja (see the first link) that if someone could reproduce this problem “please contact us here or via Gradle Community Slack”. So I thought I should post here.

Ah, I see, but it was "here or there", not "and" :-D Anyway, pinging @Anze Sodja then, just in case. :-)

Honestly, I missed the or part too (until now). I just saw the request for slack contact and did it.

🤷‍♂️🙂

Thanks for the reproducer. 🙂 We discussed this a bit today again and I think Lóránt answered there in the issue. We still need to try to reproduce it, though. But I think we have an agreement that we need to implement a different logic for Windows that will use "file locks" instead of "atomic move" semantics.

Ok thanks. I’ll keep this simply as notification, and move all discussion to github.