-
Notifications
You must be signed in to change notification settings - Fork 161
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
"Cannot find packaged artefact" error after upgrading to version 5.93.1 #646
Comments
Thanks for the report. I switched to the new JetBrains Gradle plugin for this release, which has a lot of breaking changes, so I presume it’s a side-effect of this. I’ve pulled the new version until I can get the time to debug this, sorry for all the hassle. I’m also on Mac but using Community 2024.2 - so I wonder if there’s something significant there, given the IDEA major version is shown in the erroring path. |
Yes, I just installed version 2024.2 and now the error is gone. So there must be a breaking change in the IntelliJ APIs. But with 2024.2 I had some issues with massive CPU usage (not related to the Checkstyle plugin, but to IntelliJ itself), so I downgraded back to version 2024.1. I continue to monitor the CPU usage, but if it continues to be a problem, I will have to downgrade again. |
Thanks, that’s a useful data point. I’ll certainly aim to get it working on 2024.1! |
I have the same problem (but version 5.93.0) and another library
|
5.93.0 was also built with the new Gradle plugin, so I'd expect it to show the same problems. Both 5.93.0 and 5.93.1 should have been removed from the plugin repo now. @is-ivanov to help with tracing this, could you please tell me which version of IDEA you're using, and on which platform? Thank you |
IntelliJ IDEA 2024.2.0.1 (Ultimate Edition) |
I'm having problems reproducing this - 2024.1 is working fine in my testing, with both an upgrade and a clean plugin install. The directory structure appears correct as well. The only difference I'm aware of is that I'm install the artefact from disc (as, of course, it's no longer on the JB plugin repo).
What I'd expect, for the record:
|
Belay that. I think I've found the problem area, if not the cause - looks to be a packaging & upload issue. It's building fine locally, but the artefact being generated during the release build on GHA appears to be about 1Mb in size (it should be closer to 80Mb). |
There's something odd, as I can't reproduce it locally, or in Docker, or with a fresh checkout. So still working on this, but no answers yet. |
It is, of course, a case-sensitivity problem. The sandbox path was capitalised in the old plugin; it is now lower-case. Hence, building on MacOS (or Docker when you're sharing the working directory) doesn't break, but pushing it to CI on Debian does. Bar further problems, I hope to have a fix out shortly. |
…sitive FSs (in particular, CI) (#646)
Fix in 5.93.4 🤞 |
After the update to version 5.93.1, I get the following error for every scan:
IntelliJ about:
The problem seems similar to #605 , but reinstalling the whole plugin didn't solve the problem in this case.
The text was updated successfully, but these errors were encountered: