-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Not able to Run->Debug in Intellij Idea 2022.1, it shut's down immediately with exit code 2 #11261
Comments
Just wanted to let you know that we have the same issue, maybe more information helps us track down the issue. In our case, a full reboot of Windows temporarily solves the issue -- it is reappearing though, and an IntelliJ restart does not help. Really strange... In our case However, using the run configuration from IntelliJ fails (both for "Run" and "Debug"). It only prints the exit code, there is no further information. What's also strange: This is only a problem on my colleague's machine, everythings works alright for me. Play Version2.8.8; 2.8.15 SBT version1.5.5; 1.6.2 Java Version11.0.13 (Eclipse Adoptium Temurin) Operating SystemWindows 10 IntelliJ versions2021.3; 2022.1 |
My guess is that this was introduced in latest IntelliJ 2022.1, maybe open a bug there? See https://youtrack.jetbrains.com/issues?q=Subsystem:%20%7BPlay%20Framework%7D |
Can you confirm this is working with 2021.3? |
We will check and report back, thanks for the quick reply. We had the issue in 2021.3 but that was probably still with Play 2.8.8 and is thus fixed with #11086 |
Yeah, it's easy to get confused, so please make sure to alway test with latest 2.8.15, thanks! |
The issue is also present in IntelliJ 2021.3 ( We've also tested in 2021.3.3 ( The output of the run (for 2021.3) was:
Workaround - sbt shell is relatedHowever, it seems that this is related to an sbt-shell running (in the Interesting enough, this is independent of the "use sbt for project reload/builds" settings. => We have a workaround - both in 2021.3.3 and 2022.1 it works when first closing the |
I have the same issue. I got it today when had to |
I need to get my hands on a windows machine to test this. However, it might make sense to open a bug report in the JetBrain issue tracker (youtrack)? |
One more note: it seems that whenever the |
I have reported it to JetBrains as well: |
FYI, a workaround to this issue is to run the application as a "Play2 App" instead of SBT Task, and add this to JVM params: -Dsbt.server.forcestart=true |
Another workaround that seems to work for my team is using |
Is this still a problem in IntelliJ IDEA 2023.3 on Windows? |
I only did a very quick check - this may well be a different issue (Windows?). However, I still can't launch the play app while the sbt shell is active. I get the following error:
It works if I close the sbt shell first. |
I face what seems like a similar issue as #11086 with 2.8.15 and the latest IntelliJ Idea (IntelliJ IDEA 2022.1 (Ultimate Edition) Build #IU-221.5080.210, built on April 12, 2022). Just like with the problem above it works fine running
sbt run
but not Idea->Run->Debug.It works perfectly well on linux, but not on two different Windows computers.
Reproduce:
sbt new playframework/play-java-seed.g8
"Use Play 2 compiler for this project" is disabled (tried both).
When starting the debugger it builds just fine, but when it after building opens the debugger console it exits immediately:
Closing Idea and running call sbt run > test.log 2>&1 works, but maybe the first error is the problem? Output from test.log:
I tried SBT versions from 1.4.0->1.6.2 and also downgrading Play back to 2.8.8.
-->
Play Version
2.8.8 -> 2.8.14
API
Java 11.0.14
Operating System
Windows 10
The text was updated successfully, but these errors were encountered: