-
Notifications
You must be signed in to change notification settings - Fork 153
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
[infinitest-intellij] NullPointerException in applyInformationWithProgress() in Idea 2017.2 #233
Comments
This is still happening with updated builds. I can't pin point the exact trigger that causes it to throw this error, but it appears to be happening while watching for changes. Doesn't appear to block running of the tests though. Setup Details:IDE: IntelliJ IDEA 2017.3.4 (Ultimate Edition) - Build #IU-173.4548.28, built on January 29, 2018 Exception Stacktrace:
|
I spotted that the problem occurs only if I have more than one open idea windows (and working on "the second one"). I haven't encountered that error with just one Idea window. Probably the plugin doesn't take into account information about the current window. Still occurs (with 2+ windows) with IC- 2018.3.1 and Infinitest 5.2.0. |
@szpak just FYI; it happens if you have open any jetbrains tool as the second window (which, in some cases, does not have infinitest plugin) e.g. WebStorm |
@szpak it also happens if you have only one IDE open:
|
Hmm, strange. Do you have a balloon visible in that case or the notifications are completely broken? |
@szpak This is the IDE version info:
|
I got a similar error with IDEA 2022.2 (only one window open)
|
Store the pass in the editor instead of calling fileEditor.getBackgroundHighlighter().createPassesForEditor(), that method recreates the passes and must not be called from the EDT while highlightingPass.applyInformationToEditor() must be called from the EDT. fixes infinitest#233 fixes infinitest#274
Occasionally I observe the following exception using Infinitest plugin 5.1.116 with Intelluj Idea Community 2017.2 (build 172.3317.53). In general the plugin seems to work fine.
I haven't seen that in the previous version, but I was using older patched version due to #192, so it might not be affected.
The full stacktrace:
The text was updated successfully, but these errors were encountered: