-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotless 6.0.4 fails with Object.hashCode
exception
#1024
Comments
I think this issue was introduced in 82c3435 |
Hmm, very strange. I can confirm on my machine that the mockito build with Spotless stacktrace
The null is from L71 of the little section below. It's passing null on a get() of this ConcurrentHashMap. Updating Gradle to Can you update Gradle to |
I suppose we can yes, but not sure when I can get to it. Do you mind opening a PR for it if you already have a local working version of it? |
I am a maintainer for Spotless, not every other project that uses Spotless :) I very much appreciate the reproducible test case, probably others will bump into this issue too, so this will be helpful to them too. Feel free to post back if more info becomes available, but I'm closing as "fixed by Gradle 7.3.1". |
This release officially supports Java 17 and is supposedly fixing diffplug/spotless#1024
Ah apologies I thought you already had a local branch working with Gradle 7.3.1, so I was mostly curious if you could upload that. We are upgrading to version 7.3.1 in mockito/mockito#2509 and hopefully that unblocks mockito/mockito#2501 |
This release officially supports Java 17 and is supposedly fixing diffplug/spotless#1024
This sounds a bit similar to #1087 but maybe it is only superficially related. |
Today, I received a Dependabot update for Spotless on Mockito: mockito/mockito#2501 The build failed (https://github.com/mockito/mockito/runs/4450375421?check_suite_focus=true) with the following exception:
Gradle version: 7.2
Spotless: 6.0.4 (works fine with 6.0.2)
Configuration:
The text was updated successfully, but these errors were encountered: