Running tests suddenly started failing silently in a single Java project - intellij-idea

I have a project that I've been working on for a few weeks with no problems. I've made no changes at all since it was working yesterday morning, but since yesterday afternoon running any test in just that project fails silently.
I see (or rather, don't see) the same thing regardless of how I run a test - Ctrl+Shift+F10, right-clicking in the code view or in the project view and choosing 'Run ...Test', or clicking the 'Play' button in the top-right corner on a previously-working test. Interestingly, in this last case, I only had one chance to do it - the 'Play' button is now greyed-out, even if I create a new run configuration. The same is true for running, debugging and 'run with coverage'.
When I run a test, I get no feedback whatsoever, the test doesn't run, nothing appears in the status bar or the idea.log file.
This is in a multi-module Maven project, and I see the same for all tests in all submodules of that project. I am running 2018.1.6 (Ultimate Edition) on Windows 7. I updated to 2018.1.6 a couple of days ago, but it's been working fine since then.
The tests in all my other projects work perfectly well.
I've restarted IntelliJ, invalidating the caches, I've re-imported the project, and even re-cloned it and created a new copy of it from scratch. I've restarted my machine.
A colleague had experienced the same problem in a different project (that project works fine for me) with 2018.1.5 a few days ago, and has resolved it by completely uninstalling IntelliJ and reinstalling 2018.1.4. I'd rather not resort to that if possible.

Related

NPM run dev successful in vscode but not terminal (contenlayer + Nextjs)

I am a bit at a loss on this one. Everything in my terminal (hyper) was working just fine the other day until I closed out of it. I came in to launch a Nextjs app I had been working on and now npm run dev just hangs up and doesn't actually start. The strange thing (to me) is that Visual Studio Code's integrated terminal seems to run just fine (and much quicker).
So far, the only packages I have added are contentlayer and next-contentlayer besides the default nextjs packages. Basically, contentlayer looks for md files (in a difined dir) and then generates an api for them. Strangely this seems to work everywhere else but in my actual standalone terminal.
Hyper.js:
Visual Studio code integrated terminal:
I have found that if I remove makeSource from the contentlayer.config.ts file, next dev will still run. At this point I could just use vscode, but I would really like to figure out the issue on all of this.

Intellij IDEA is not remembering the license/activation code or the opened projects after doing a restart

I have entered my Jetbrains license and already created a project three times now. I imported IDE settings which requires a restart and when the restart happens poof the license/activation key is gone as well as the project that had already been opened.
This is a strange behavior. I have installed and used the jetbrains products many dozens of times on different computers and had not seen this before. In fact DataSpell and Pycharm are working normally on this same computer.
I am on macOS Monterey 12.5.1
This problem has been identified as being due to using the "import Settings" feature. When I do that and restart Intellij then the activation code and in fact all past knowledge of my installation are gone. #CrazyCoder

Grails 4-IntelliJ IDEA version 19 increased compilation time

We are using IntelliJ IDEA version 19 towards development of a web application in Grails 4 framework. The issue we are facing is, while undertaking code changes in controller, services and domain the IntelliJ IDEA version 19 is compiling the entire project, i.e. the project gets restarted and the entire project gets complied from the beginning as a result of which the whole process of compilation is taking longer time. Where else compilation of GSP and JavaScript files are happening dynamically without restarting the entire project.
It is requested the way ahead for the said issue to be provided.

How can I stop my IAR ide from hanging when changing build configurations

I have come across this particular problem several times across several versions of the IAR embedded workbench (EW430 5.40.7 [EW 6.0], EW430 5.51.2 [EW 6.4], EW430 6.20.1 [EW 7.0]), but each time only after a long period of having no problems. The problem doesn't seem to have affected the other firmware developers in the office, so no help can be offered there. I'm currently on Windows 10, but the problems first occurred when I was on Windows 8.1 (same PC.)
The problem is that, for no obvious trigger, the IAR ide will start to hang until terminated (or it will just crash on one of the EW versions) on any attempt to change the active build configuration in MSP430 projects using the emulator.
From my testing, it appears to be directly related to something the IDE is doing with the emulator, as when the build configuration is changed, I can see the emulator menu in the menu bar disappear, then the hang happens. Under normal circumstances, the menu will disappear, but then reappear once the other debug configuration is completely loaded.
I have tried the default project "flashing the LED" to see if it was only my project - but if I select the msp430x4xx (C) - Debug, right click it and select "Set as Active" from the context menu, to make this the active project, the IDE also hung. I then reopened the EW IDE, and opened the LED flashing project again. The original 1xx asm project was the active project.
I then changed the settings of the 4xx (C) Debug project (without making it the active project) from the emulator to the simulator, and clicked OK. The program did NOT crash.
I then set the 4xx (C) Debug project as the active project and it did NOT crash. The simulator even runs without problems.
The version of the FET firmware didn't change from when the IDE worked correctly to when it didn't, and the FET is not even used at this point. It can be completely disconnected and the same results will occur.
I have tried the following, without success:
erasing the files in my project folder's settings subfolder
erasing the *.dep files in the project folder.
deleting the IarIdePm.ini file from AppData\Roaming\IAR Embedded Workbench
making sure none of the project files are read-only
reinstalling the program to the same location
removing and reinstalling the program to the same location.
What does solve the problem (until it reoccurs) is to reinstall the program, but to a different directory (for e.g., the default directory will be in program files (x86)\IAR Systems\Embedded Workbench x.x. Installing again into program files (x86)\IAR Systems\EWx (just so it is different) allowed that installation to work, but the old installation continued to fail.
Best advice so far (from our support person) has been to do the above, install to another directory and live with it, as it doesn't happen often.
Since it has happened to me on 3 occasions with 3 different versions of the program, I would like to know how to fix or prevent it! If anyone could offer anything to try (or even better, a straight solution :)) that would be greatly appreciated!
Cheers!
Since newer versions and updates on W10, it seems that old compatibilities are being removed from this OS. I have no direct solution for this problem since Microsoft does not promise support for old software and hardware. Even I tried to find a solution for that problem, and I found on the IAR website a list of IDE's and their compatible versions. (remember, old versions are not compatible)
( https://www.iar.com/knowledge/support/technical-notes/ide/windows-10-and-iar-embedded-workbench/ )
You will need to update your IDE and program version to a newer version if you plan to continue to use this IDE natively on Windows 10 or you may use Virtual machines with an old operational system (like Windows 7) to compile your program on old IDE.
P.S.1 I manually uninstalled KB4592449 recently updated and the program return to work natively. Probably it will continue working until this update (or other similar) being installed again on the computer, but probably there is any vulnerability that the computer will be exposed to, and in this case, I'm paying the price.
P.S.2 KB4580325 promotes the same behavior in IAR 5.11 on windows 10. Both KB's implement securities about the flash player - that I Don't use - then, I can securely uninstall it.
P.S.3 Since I updated my windows up to Windows 10 version 21H1 (compilation 19043.1165) AND I configured Windows defender to not be monitoring IAR IDE (IarIdePM.exe) disabling all protections available, everything works fine. But Remember: my program is original, not cracked or altered by anything, then I am secure to do what I did.
It is a 'natural' that software problem. Not found way of fixing it. The solution temporary is modify manually the file .eww for change of project active. The ultimate solution is to use another development environment.

Launch Grails 3 app from IntelliJ w/ auto-reloading enabled

It looks like IntelliJ's (Ultimate EAP 15) support for Grails 3 is in the early stages yet. If I do Run -> Debug 'Grails:My App', I'm able to launch an app from inside IntelliJ, I can set breakpoints and it works as expected.
If I make changes however, I see in the console that the file is recompiled, but when I hit reload in the browser, I don't see the changes reflected there. I have to stop and restart the app in IntelliJ before I see them. Anyone know how I can get the auto-reloading working?
After chasing this for a week, this post finally provided an explanation.
It's actually a Grails issue, not a problem with IntelliJ's Grails integration: spaces in a file's path will break automatic reloading. Renaming my project from Grails Demo to GrailsDemo got everything straighted out. (Storing a project in a folder like My Documents will also cause trouble.) The post's author indicates that this started with version 2.4.4 and it's still happening for me in 3.0.4.