I restarted VSCode because there were some problems with it, and now the test button on the left, the one that looks like a flask, has disappeared! I tried to run the command "Test: Run All Tests", but I get a message "No tests found in this workspace. You may need to install a test provider extension". Did I just accidentally uninstall test support in VSCode??? I can still run pytest from the command line and that works fine.
EDIT
Please read my own answer below.
OK I found out the problem myself. It seems that there is another Python executable on my Windows machine, which seems to have come with VSCode itself, at C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe. Somehow when I restarted VSCode, that Python executable was selected, and it didn't have pytest or even unittest or anything I don't think, so I guess VSCode saw that there was no testing capability at all and didn't bother showing the test button. It seems insane that VSCode comes with its own Python executable though, I wonder why that is.
EDIT
Oh oops it's Visual Studio that came with the Python executable, not VSCode, obviously as the path suggests. My bad.
Related
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.
I recently installed MacOS BigSur, and updated to the latest version of PyCharm, but I think it totally broke it.
Indeed, I mostly use Selenium, and I had trouble installing the package, but I managed to do it via the mac terminal, using this command:
/Users/inakivignal/PycharmProjects/NikeFP/venv/bin/python -m pip install selenium
After that, it shows me errors from importing webdriver and even importing random. I don't know what else to do, because before it imported them directly from packages. I verified and selenium is indeed installed as an interpreter in this project.
I'll attach what it shows me when i put this code:
code
I really don't know what is wrong with my PyCharm, if any of you could help me I would really appreciate it.
Thanks
If you are sure that it is installed, you could right click on the error, then take the option "install package Selenium" looking like this: https://gyazo.com/2f7ed596192c772d164652e2a5fdbc0b
not sure if this helps but worth a try, also had problems with this
I killed an "idea" process in terminal after Intellij had frozen. The idea.sh script was missing after I killed the process (I ran a find command and checked other directories & the trash but no luck). I have since copied my friends "idea.sh" script into its former location. Now when I run ./idea.sh I get:
"Error: Could not find or load main class com.intellij.idea.Main".
I have tried searching for this class as well but got no results. Google has no info and I'm not very informed on Intellij.
Any hints on what I might need to do to avoid reinstalling Intellij?
I had the same issue after updating the android studio. I was not able to launch it from click on Android Studio icon and after running ./studio.sh it was giving me the same error
I do this to solve my issue
I downloaded the studio and install it in the new directory.
After installation success, copy all the files & folders and paste and replace it into the old location where the studio was installed.
And it is working fine.
Is it possible to show warnings (not used variables / typo), errors and an overview about my created variables and functions in an open file?
I have installed the newest Visual Studio Code IDE but if I press Ctrl + P and then !, my VSCode says there are no results. It doesn't know !-command and other commands I found in the internet.
What extension/addon do I have to install to see this? It would be great if I could see this in a separate window without using Ctrl + P and if the IDE would mark positions with warnings/errors in my open code as Eclipse-IDE can do.
Use Eslint. Install it globally using the following command
npm install -g eslint
It will show all possible warnings based on the rule sets given, while you are coding. Moreover VSCode is not an IDE it's just Code Editor like Sublime.
The main difference here is the word IDE...Eclipse is an IDE and is the most widely used Java IDE, but, Visual Studio Code is not an IDE, but, a code editor.
If you want to try a Microsoft IDE, you can download
Visual Studio Community, a fully-featured, extensible, free IDE for creating modern applications for Android, iOS, Windows, as well as web applications and cloud services https://www.visualstudio.com/vs/community/
Is it possible to show warnings (not used variables / typo), errors [...] in an open file?
The VS Code extension for quick-lint-js can show you syntax errors and misspelled variable names. It requires no configuration. (ESLint requires per-project configuration.)
At this moment, quick-lint-js doesn't tell you about unused variables.
I'm not that up on VB.NET, the application I'm working on was not written by myself.
It works fine through the IDE but once I run it from the exe it gives me the above error.
Any clues?
This is really hacking me off!
The only user defined break point that I can think of is
Debugger.Break()
So, I would suspect that the .exe is compiled in debug mode. I would recommend Reflector to look at the code and find out for sure whether or not there is a Debugger.Break() somewhere in there.
Afaik, the only way this could occur if you are compiling under debugging settings. You should be able to fix it by doing the following:
Right-click your solution on the
solution explorer.
Select configuration properties.
At the top of the dialog box there should be a
combobox, which will most likely say
"Active(Debug)".
Click on the dropdown and select release.
Ok out of everything.
Build > Rebuild Solution.
Source: p2p.wrox.com
I believe the exe file was compiled using the "Debug" setting. Try changing the Build setting to Release and do a full build (rebuild) of the project. Then try to run the executable file. It should then run normally.
The reason you see that error is because when you normally compile and run applications in Visual Studio, it compiles a Debug build of the executable. The different between a debug build and a release build is that the debug build has additional information added to it, by the compiler, so it can be debugged properly.
I would suggest looking for stop in your code. That is what generated this error for me.