So earlier I was using node version v13.6 bascially because I am on windows 7 and node.js supports only windows 7 till v13.6 . So what I did was I downloaded the node.js latest version(v14.x.x) in '.zip' package and replaced all the files in the nodejs folder with the newer version file. I also know how to set environment variable but how can I set NODE_SKIP_PLATFORM_CHECK to 1 from the system properties in order to bypass the and run the latest version of node.jsenter image description here?
This work for me
Go to System-Properties (run: systempropertiesadvanced.exe), in
Advanced tab, click Environment Variables.
Still on the System variables, click 'New', add "NODE_PATH" with value "C:\nodejs64\node_modules", and click OK.
click 'New' again, add "NODE_SKIP_PLATFORM_CHECK" with value "1", and click OK.
Click OK of all dialogs close.
Restart your machine, so explore and cmd will get the fresh set of variables.
Related
Specs:
Windows 10 Home 21H2
CPU Intel i7-8700k
Motherboard ASUS Prime Z370-P II
Visual Studio Code v1.65.2
Node v16.14.2.
npm v8.5.0
The Problem:
When I run Pick Color ...
This happens
How I got here:
I installed node (and npm) as part of a course, from the official website, to use a TypeScript compiler.
In the process Chocolatey and something about Python was also installed. I think I remember seeing some errors in the script, but I'm very new to all of this. Despite that, both are in paths, as shown later.
Also had to use PowerShell and run
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
I checked the installation
Node version
Now this is what happens when I try to use the Color Picker extension. First, the installation guide says
this.
PATH is ok, as shown in the following pictures.
Node Version Manager? Don't remember using that.
Command Pallete, ext install, "Color Picker" not on the list.
Paths:
User Variables Path and
System Path
VS Code:
Trying ext install in the command pallete
I'm very sorry for this last screenshots in spanish.
Lastly I found this old issue on GitHub but I couldn't solve my problem with it:
(Gonna leave link in the comments as I can't go beyond 8 links in my post.)
Do you need this extension? Probably something buggy that will cause you problems with every upgrade. You already have a similar and cleaner solution as a VSCode default:
Just hover over a color and the little square icon next to it in a CSS or SASS/SCSS file, and you'll see the picker pop up. For changing from RGB(A) to HEX and other types, just click the header where you see rgba(84, ...) in the screenshot.
I'm using Windows 10 and Excel 2016 and I tried to install the Windows Common Controls (SP6) using the file mscomctl.ocx.
I performed the following steps:
Copy the mscomctl.ocx file into the folder C:\Windows\SysWow64
Register the file with the cmd prompt regsvr32 C:\Windows\SysWow64\mscomctl.ocx
Referenced the mscomctl.ocx in VBA which appeard then in the list with a checked box
Checked the registry and theres only an entry for Version 2
Step N. 5 would have been adding the control to the Standard controls but None of the common controls does appear in the list.
Does anybody have experienced similary issues?
You need to make sure you install the 64 bit version of ListView otherwise you will not be able to add it.
Actually the ListView and TreeView are already installed by default (at my Win 10, Excel 2016 x64 1902). So there is no need to install something extra.
Just make sure you are on the latest update and click in VBE menu: Extras » Additional Controls … where you should find Microsoft ListView Control, version 6.0:
If you don't find it there is probably something wrong with your installed Office, try to update first, if it doesn't help repair/re-install Office.
This has been bothering me for a long time. I am unable to debug SSIS package efficiently because the Variables collection of SSIS package is always empty.
SS of Locals window showing blank value for Variables collection variable
Updated after userfl89 gave an alternative solution
Also, the watch window is showing unable to evaluate the expression error message
I found a similar issue in general VS development environments (C#, VB.NET) and tried suggestions/answers. For example, changing Debug->Options->Debugging-> check Managed c++ compatibility mode (see ss below) but it did not work for me.
SS of debugging setting:
I have also tried to run in both 64bit mode and 32bit mode, but this also did not work. However, I can see variable values inside script task written in C# code. It has become a painful task to debug packages. Please someone help.
Environment:
Windows 7 Enterprise (64bit)
Visual studio 2012 for Data Tools (version 11.0.6xxx)
.Net Framework 4.6
I'm assuming that you already set a breakpoint? When the package hits the breakpoint, on the top menu go to Debug > Windows > Locals and from here expand the top variables node, however it looks like you've already done this. You can also view the variables values in the Watch windows by typing the name of the variable in the Name field when the breakpoint is reached. This will only be the variable name, not the #[User::Variable] syntax.
I have been using Pycharm for years and have never had any problem. However, after my most recent PyCharm update I can no longer configure the interpreter.
Also each time I create a new project it creates a vent directory under my project. When I go to File/Default Settings/Project Interpreter, I am provided with new options.
In this window it allows you to configure a virtual environment, the conda environment, and the system interpreter. I am assuming that I should configure the system interpreter. From there I point PyCharm to the interpreter on my Mac at /usr/local/Cellar/python3/3.6.3/bin/python3 and hit OK.
It then takes me back to the main window where it shows the path in the project interpreter. At this point I hit apply and get a message:
Cannot Save Settings please use a different SDK name
It doesn't matter which interpreter I choose, I get the same message. Has anyone else come up with the same problem and how do I fix this?
Interestingly my old projects still work correctly.
I had the same problem while setting up the virtual environment for my project and no matter if I create a new virtual environment or select an existing one, I get the warning:
"Cannot Save Settings please use a different SDK name"
Finally I found the solution:
Click on the project interpreter dropdown and select show all.... There you might be having multiple virtual environments with same name. Now here is the conflict you need to fix manually by renaming them so every item has the unique name.
I ran into this issue when trying to get docker up and running with Pycharm 2018.1 and using the container's Interpreter. I would get the error below.
"Cannot Save Settings please use a different SDK name"
The issue I had was due to having multiple python interpreters of the same name.
Under Pycharm || Preferences || Project Interpreter
Click "show all" within the Project Interpreter dropdown and then delete any / all interpreters that you don't need.
How fix this in Windows 10:
close Pycharm .
delete this file: C:\Users\<username>\.PyCharmCE2018.3\config\options\jdk.table.xml
open Pycahrm again and load all python interceptors again.
Jon; I too noticed the difference in the latest version of PyCharm. It seems that it now has an affinity for the latest tool 'venv'. When you create an interpreter - that is what you get.
You can still create a virtualenv manually and point it there instead. I haven't looked into pointing it to a base python-bin because (frankly) you shouldn't generally do it.
My advice (and my proposed answer) is to embrace the change and let it create a 'venv' for you. From there, do all of your installs by "alt-F12". That will open a console with your virtual environment activate -- so your PIP installs into the virtual environment.
Once I began using virtual environments, I never looked back. It has made life much easier in the python world. Pycharm seems to know this as well and is trying to really encourage you to do the right thing.
SteveJ
[Edit Alternate way to get to terminal]
This may be a known issue of PyCharm and using the method of the accepted answer may not resolve it. Please see https://youtrack.jetbrains.com/issue/PY-27251.
You can close Pycharm and remove jdk.table.xml file from ~/Library/Preferences/.PyCharm2018.1/options directory (Mac version), then start PyCharm again.
Warning: By doing this, all your existing setup of python interpreters will be erased and you need to re-setup them again.
I had same error:
I deleted all invalid project interpreters ( they are red)
then I did https://stackoverflow.com/a/60583928/3842788
You cannot have 2 or more virtual environments with same name. Even if you have projects with same name stored at 2 different places, please give unique name to its venv. This will solve your problem.
To check all the virtual environments:
Go to File >> Settings >> Project: your_project_name >> Project Interpreter
And rename the venv name.
Go to Project > Project Interpreter > Select the dropdown menu > "Show All".
For me, there were several Python environments, two of which were red with an tag. Remove the envs that are red / have an tag, select the remaining valid one, and re-apply settings.
In my case, I moved my project to a different location and PyCharm started complaining about Cannot Save Settings please use a different SDK name. At the top of the main editor, it asks me to Configure Project Interpreter. I clicked it, and then ...
My solution
Remove all existing interpreters that are marked as invalid in the preference.
Select the interpreter in the moved venv subfolder in my project.
Without doing both, I kept getting the same "SDK name" error. It seemed that the project thinks that it already has an interpreter called "python.exe", if you don't actively remove all "invalid" ones.
I solved this issue by cleaning the Pycharm memory cache
I had a lot of trouble while building opencv 3.1 from source code with Python 3.5 -32 bit on Windows 10. For any custom build, its a painfully long procedure which has to be followed meticulously. My purpose was to enable Ximea support with OpenCV for which I needed to custom build it.
Now that I have finally nailed it, I have decided to put the complete procedure here in case someone wants to repeat it. Believe me, it will save a lot of trouble. I will post the procedure in the answer.
Procedure to custom build opencv 3.1 for Python 3.5 - 32 bit on Windows 10
Download Python3.5.2
Install numpy (atleast), scipy, matplotlib from http://www.lfd.uci.edu/~gohlke/pythonlibs/. All libraries should be 32-bit version for Python 3.5 version
Install CMake (3.4.1 or later version recommended)
Download opencv3.1 for windows from http://opencv.org/downloads.html
Extract it to a folder where you want to build the library. In this example it is C:\opencv_310
After extracting, you will get two folders - build and source. Pre-build library has support for Python 2.7. We will need to build the library from source code for Python 3.5
Make new folder. In this example, it is named as 'build_custom'
Open CMake and put path for source code 'C:/opencv_310/opencv/sources'
Put path for building the binaries 'C:/opencv_310/opencv/build_custom'
Click Configure
Enter the path for Python3.5
PYTHON3_EXECUTABLE 'C:/Python35/python.exe'
PYTHON3_INCLUDE_DIR 'C:/Python35/lib/site-packages/numpy/core/include'
PYTHON3_LIBRARY 'C:/Python35/libs/python35.lib'
PYTHON3_NUMPY_INCLUDE_DIRS 'C:/Python35/lib/site-packages/numpy/core/include'
PYTHON3_PACKAGES_PATH 'C:/Python35/Lib/site-packages'
In my case, I wanted to enable Ximea camera with OpenCV so I ticked 'WITH_XIMEA'
Untick BUILD_EXAMPLES, BUILD_PERF_TESTS, BUILD_TESTS
Click Configure
Make sure that 'BUILD_opencv_python3' is ticked on. Click Configure again.
Make sure there are no red lines after configure. Now click Generate.
In my case I was trying to get Ximea camera enabled with OpenCV. For that purpose before buliding solution with VisualStudio, make sure you add 'C:\XIMEA\API\x86\' to Environment Variables first.
Go to folder 'C:\opencv_310\opencv\build_custom'
Click on "OpenCV.sln" and open it in Visual Studio (I had VisualStudio 10 installed on my system)
In VisualStudio, make sure you have 'open_python3' in 'bindings' section
Click on Build -> Build Solution. It will take some time to build all the libraries. At the end of build, it should display "29 succeeded, 1 failed"
Number of succeeded build libraries may vary. But for failed, only 1 should fail where python35_d.lib is not found, mainly because Python3.5 doesnt have debug mode library.
Now change from Debug to Release mode and click on the green arrow next to it.
It will build all the libraries in release mode and this time it should say "30 succeeded, 0 failed"
Now environment variables are to be changed. Go to 'My Computer -> Right click -> Properties -> Advanced system settings -> Environment Variables'
In user variables, add NEW, Variable Name = 'OPENCV_DIR', Variable Path = 'C:\opencv_310\opencv\build_custom'
In system variables, add NEW, Variable Name = 'C:\opencv_310\opencv\build_custom\bin'. Click OK
Check if the changes in environment variables are registered. Open command prompt and enter PATH (check for system variable) and system opencv)
Now go to the folder 'C:\opencv_310\opencv\build_custom\lib\python3\Release' and copy 'cv2.cp35-win32.pyd' to 'C:\Python35\Lib\site-packages'
Now go to the folder 'C:\opencv_310\opencv\build_custom\bin\Release' and copy 17 DLLs to ''C:\Python35\Lib\site-packages'
Copy 'opencv_ffmpeg310.dll' from the same folder to 'C:\Python35'
Now go to the directory where Python is installed - "C:\Python35". Open python console by entering 'python'
Once Python console is open, enter 'import cv2'. You should get no error.
Enter 'print(cv2.getBuildInformation())'. It will display all the build properties for OpenCV.
In my case I was trying to get Ximea camera enabled with OpenCV. For that purpose before buliding solution with VisualStudio, make sure you add 'C:\XIMEA\API\x86\' to Environment Variables first.
Or else you will get error while building the solution - 'xiApi.h' not found.
Common errors
1. Make sure everything is 32 bit
Make sure User Variable and System Variable path are correct (This part costed me a lot of time)
Make sure no red lines are present while configuring CMake
Make sure BUILD_opencv_python3 is ticked on
Make sure 'cv2.cp35-win32.pyd' and all 17 DLLs are copied to the right place