On 21.07.25 23:08, Jonny wrote:
I've traced the issue back to 33064484cc043bfb7c2ad75ee8fccbcbc6329b76. I think I've hit upon a fix <https://github.com/apache/groovy/pull/2270>, pending review. Apologies for doing this on the release thread. Feel free to tell me that I'm out of order or just need to wait for the next release train. 😅
I am trying to understand the bug behind this, but I fail a bit.. for this to happen it needs a reload by GSE? Then we imho leave something somewhere dirty, or we cache and the cache is not considering the change.
From what I can see I find Collections.emptyMap() in ResolveVisitor for visitField and visitProperty, which is most likely causing the exception on put. But how?
I am for applying the patch, just I have the feeling the real bug is not fixed with this.
bye Jochen
