Log analyzer blows up java.lang.Integer cannot be cast to java.lang.String
When download logs, double click log, it opens a warning dialog “Error, java.lang.Integer cannot be cast to java.lang.String” and does not open the log.
Comments (12)
-
repo owner -
repo owner Could you also provide your
idea.log
? You can get it using Help>Show Log in Finder. -
reporter - attached idea.log
-
reporter - attached IntelliJ version.png
-
repo owner - attached IlluminatedCloud2.zip
Thanks, Karel. From the log I can see what's blowing up, but it doesn't make sense why it would be happening.
I've attached a build that should work around the issue for you. You can install it by downloading
IlluminatedCloud2.zip
--don't extract it--and use Preferences>Plugins>Install plugin from disk (under the gear drop-down).If possible I would like to have access to the log that causes this issue so that I can do some root cause analysis. Could you share that via email?
-
reporter Thanks. I’ve restarted IntelliJ and the problem went away. I should have made it as first choice. So I did not use your work around but thank you for that anyway. Maybe the logs list did not refresh properly, not sure.
-
repo owner Hmmm...okay. Well, the change I have would at least handle this more gracefully if it were ever to occur again. I'll include it in the next build just in case.
-
reporter I should have installed the fix yesterday, the same problem happened again. But the download link is not available anymore
, it says That link has no power here. After starting IntelliJ today, I was able to download my logs in the “Log analyzer” OK, it opened each log properly. Then after a few Refreshes it rejected to open one of the logs displaying the nasty “Integer cannot be cast” error. Then after letting it relax for a while (30 minutes) I hit Refresh again, and then the same malfunctioning log could be opened normally. So no need to restart IntelliJ. Maybe something wrong on my side or in our sandbox, but that error never happened in previous versions of IntelliJ / Illuminated cloud which I both updated just recently. If you provide the fix I’ll try it immediately, since I depend on the logs so much.
-
repo owner - attached IlluminatedCloud2.zip
Sure, no problem. This is the build I'm prepping for release right now. It lacks the release notes and version number update, but otherwise it should be the same. Feel free to install it and to take the update later today which should be the official release of the same thing.
-
reporter I have installed the fix, will test similar test opening the logs (same daily routine) tomorrow.
-
repo owner - changed status to resolved
Delivered in 2.0.7.5.
-
reporter I’ve done the same checking logs daily routine today and the issue did not happen, the fix probably helped. Thank you.
- Log in to comment
Karel, it would help to have access to the actual log that causes this. Can you provide that? Feel free to email it to support@illuminatedcloud.com if it contains sensitive info you'd prefer not to post here.