Recently got a new computer with "IntelliJ 2021.1.3 CE" installed, but somehow the terminal console is printing redundant message instead of "updating" messages.
I have pointed my Terminal's Shellpath to "E:\git\bin\bash.exe", but if run the same build command with gitbash.exe, I don't run into below issues...
Thanks in advance for any helps/suggestion !!
Related
When I try to start my CLion IDE (or another JetBrains IDE, like PyCharm, IntelliJ IDEA, PHP Storm etc), it fails, and I get the following message on the console:
IDE has not been initialized yet
(after the usual JVM warning I always get before and didn't prevent the IDE from starting up.)
Why is this happening? What can I do about it?
Notes:
I have a valid license.
May be related to this (resolved) issue for IntelliJ Idea.
Another instance of the IDE may be running
While you might not see it for some reason, there is another instance of your IDE already running (probably for your own user). The error message is somewhat misleading.
Let's assume you're running CLion for example. The executable's name is clion. Look for it with the ps command: ps aux | grep -i clion, or with pgrep: pgrep clion. Then terminate it (e.g. using kill with the process ID), and re-run.
Caveat: There may not be the only scenario in which you get the same error message.
I'm using Visual Studio Professional 2013 and I'm doing some very basic windows forms application.
A month ago, I could do everything I wanted without any problem. But I started some new projects today and for absolutely no reasons, I keep getting this error message when I come to debug or compile:
Debug error BC31019 : Unable to write to output file 'path/form.exe System Error &H80070005&
It can happen simply by changing the size of a textbox or modifying the text content in a label... It's very random... And I can even do an undo (ctrl+z) and then I can debug again, but if I try again to do the thing I did that brought the error message, the same message pops again as I try to run.
After reading a little about the subject, I realized that it was because the .exe file became in read-only mode and when I try to remove it, windows wont let me.
The only thing I can do if I really want to continue, is to restart my computer every times it happens. Then I can continue just like normal as my .exe file is no longer in read-only...
I tried tor run a sfc/scannow in my command prompt to see if i had any problems with my frameworks but everything was fine.
Since, it is when i restart my pc that the bug disapears, isn't anything i can do or run somewhere to do the same thing. I need to find why the exe file goes to read-only for nothing and how to get it back to normal without having to restart my pc every time...
Please help me!
thank you
I came across the same issue and it was related to having a command line argument that VS could not find, then when i clicked stop debugging I ended up in this situation as it seemed VS kept a process running.
I could see this process in task manager but could not end it (it started with the same name as my app)
I found closing VS would release this process.
Restarting VS it would then work ok again.
there may be other ways to reproduce the issue but restarting VS seems to release the file and allow you to continue.
I set the exe properties to Read/write. No effect, but when I set app properties/settings to "Always on top" = False the issue went away and is still away.
I tried to start Eclipse, it just shows loading eclipse and then stops/crashes after a while, I haven't changed anything from before.
even I tried to replace it with other version but some thing happens, when I open it with terminal I get this error:
-- ERROR: RebelPlugin.getDefault() retured null!! Likely cause: plugin not started properly!
logout
[Process completed]
It seems like the RebelPlugin is causing issues. The simplest option is to install a new Eclipse and run that instead. You can reuse your previous workspace and the code will be untouched, so you will just loose some time.
There are other alternatives to try, but they may be a bit more advanced. From commandline you can try to uninstall the RebelPlugin and see if that makes a difference, and then reinstalling.
java -jar plugins/org.eclipse.equinox.launcher_<version>.jar
-application org.eclipse.update.core.standaloneUpdate
-command uninstall
-featureId <feature_id of rebelplugin>
-version <version>
See the Eclipse manual for more information
In previous versions of IntelliJ IDEA (like 10.5) when I successfully run an Ant script, I get a proper message like "Ant successfully done for 55s".
But now, in version 11.1.3 of IntelliJ, I don't get this kind of message, because there some warnings. I would like to suppress those warnings and just get the message that the script is done without errors.
Actually, some times I got a message like
Thank you in advance!
It's a known bug, please star/vote it in YouTrack to track the progress.
I am starting to develop a new air/html/ajax application today and for some reason my trace() output is not being printed to the console window anymore. Plus, I am also not getting any error messages printed for syntax errors or runtime errors. I tried this on a different machine and there was no problem, so it must have been something wrong with this particular machine. I was thinking it had to do with me using the flex 3 sdk, but removing that from my path variable did not help, neither did reinstalling the air sdk. If anyone has encountered this before, help would be greatly appreciated.
This is not specific to the debugger player. The availability of trace statements in the console from ADL is dependent on whether or not any one of the following settings are turned on in your mm.cfg file:
ErrorReportingEnable
TraceOutputFileEnable
Either one of those will block trace output in the console window - stderr I believe - and instead (in the case of TraceOutputFileEnable) redirect it to a log file.
More information about mm.cfg is available here.
I figured it out. It is because I installed the flash debug player. Now the error messages all go the the log file where the debug player writes to.