I recently updated python to the latest version 3.10.5 on my Windows 10 desktop using pyenv-win. Everything went fine, except when I launched jupyter lab and found out I can't access the JSON settings editor anymore. I was following the same procedure as always:
Launching jupyterlab from the terminal using the command jupyter lab
Going to the settings menu and choosing Advanced Settings Editor
The settings editor GUI is opened as always and I can change settings through the UI, but I prefer using the JSON settings file.
On the top right of the settings editor there is a button to open the JSON Settings Editor. I click it and nothing happens. This button doesn't do anything. it used to open a text editor with all the JSON settings files. Now it simply does nothing.
I tried reinstalling jupyter lab completly, including removing every custom extension and reseting all setting to the default, and it didn't help. The JSON Settings Editor button still doesn't do anything.
Can anyone explain to me why this happens and how I can fix this?
This is a bug in the latest JupyterLab release v3.4.4. I have reproduced it on 3.4.4 and opened a pull request to fix it: jupyterlab#12892. The fix should be included in the next patch release. In the meantime you can downgrade to 3.4.3 which is not affected.
Thank you for highlighting it (next time if it looks like a bug feel welcome to report directly at https://github.com/jupyterlab/jupyterlab/issues).
Edit: JupyterLab 3.4.5 is now released. Please upgrade using your package manager to get the fix.
Related
recently I installed a fresh version of the KDE neon user edition and I updated it and works fine.
I also installed the vscode Debian version and nothing is wrong.
but when I want to login with my GitHub account in vscode for configs sync it opens a firefox tab that I log in to my GitHub and authorizes the vscode and it succeeds and gets back to vscode and instead of signing in and syncing the configs it opens an empty unsaved file named something like this:
did-authenticate\?windowid\=1\&code\=6beea2fcb8a47e0ea49e\&state\=2efc5efd-9c68-4735-a4a0-fd690dd7aec0
in this path : "~/vscode:/vscode.GitHub-authentication"
and after a few seconds canceled notification appears.
I've installed vscode for Debian version 1.63.2 which people in this Github issue had the same problem in version 1.62.2 and they are saying that this problem is fixed for them in version 1.62.3.
I don't have this problem with the Microsoft account sign-in.
what am I missing?
Update:
for testing, I tried to install an extension for vscode and I pasted the URL with vscode protocol in a web browser like this (vscode:extension/GitHub.vscode-pull-request-github), and instead of opening the vscode extensions tab, it goes back to vscode and opens an empty file in the same directory ("~/vscode:/vscode.GitHub-authentication").
so this is vscodes fault that cant handle the vscode: URLs.
I found out what the problem is but I don't know how to fix it
for the record I've updated the vscode today to the 1.64.1 version and still have the problem.
enter image description here
First, you need to get the GitHub Pull Requests and Issues and GitHub extensions together. Then go to the section specified in the photo and give the details of the account and repository you are using. And then it will be fixed.
I ran into this issue myself and discovered that it's because the VS Code command-line application isn't designed to handle URLs, but local file paths. VS Code registers the vscode:// URL scheme with XDG using an appropriate *.desktop file and these URLs should be opened using the command-line program xdg-open. In Firefox, if you have not yet set a default application for vscode:// URLs, then it will ask you for a program to open it with, select /usr/bin/xdg-open. If you have already set it to a different default, you can change it as follows: go to the Menu -> Settings -> General -> Applications -> vscode -> Use other... -> Select /usr/bin/xdg-open as the program for vscode.
With the default for vscode:// URLs set to use xdg-open, then any future integration with VS Code should work naturally to open it as expected.
I have this problem with Visual Studio Code for Windows 10: I can't see the NPM scripts in the explorer sidebar.
I deleted all the extensions, uninstalled VS Code, and installed the latest version of VS Code again with no custom options and no extensions, but it didn't solve my problem; the NPM scripts menu does not appear.
How could I fix this so that the NPM Scripts menu option is shown again?
Few places to look for the NPM-Scripts explorer :
The npm-scripts explorer can be enabled or disabled with the below settings, in VSCode's settings.json:
"npm.enableScriptExplorer": false
Default value is false, change to true and it should work. Try restarting VSCode for changes to take effect(although a restart is not often required) if it doesn't show up.
Another very hard to notice place is the three dots ... in the top right corner of your project explorer (verify if NPM scripts is checked). This is something which I had experienced personally for a different extension.
Open "File > Preferences > Settings"
Search "npm script"
Toggle "Npm: Enable Script Explorer"
Close VSCode; reopen
Version 1.59.1
Go to View -> Open View and type: npm scripts:
Appreciate I may be a bit late to answer this question. For me, this was due to npm scripts not being selected to display in explorer. Once I had selected the box, the npm scripts window was available to view.
Hopefully, this has just been fixed - see https://github.com/microsoft/vscode/issues/120279#event-4631666095 and https://github.com/microsoft/vscode/issues/120279#issuecomment-824950294 seeking test verification.
It is in the Insiders now and in Stable early May, 2021. It fixed it for me.
View/Open View...
Type NPM
Click on NPM Scripts
If it still isn't working, see https://github.com/microsoft/vscode/issues/119868
Is your package.json at the root level? Does it make any difference if you open your package.json first, and then check for the view? Or try opening another .json file (or even the Release Notes has been reported as working) and then do a Reload. Otherwise, add your info to the issue.
Work around: If I leave an editor tab open with my package.json (I have one in the root, and in two other places), close and re-open VSC, then it seems to 'find' the NPM View.
TL;DR;
My VSC (1.55.2) is inconsistently showing / not showing the NPM View.
When it starts without the view, I cannot use View->Open "npm".
No option in Explorer options (...)
When it starts with the view, View->Open has a result for "npm".
Has option in Explorer options (...)
Bug report here: https://github.com/microsoft/vscode/issues/120279
Try to delete package-lock.json and restart VSCode.
In my case it worked.
It happens to me sometimes when I open VSCODE.
Whenever it happens I simply load a package.json file.
The NPM SCRIPTS menu still appears when I close the package.json file.
If that doesn't do the trick, try installing NPM-Scripts extension.
If it worked normally before but now it does not, and you have the extension installed and enabled. Then all you have to do is open your package.json file and it will be available again.
I guess this weird behavior happens when you disable all your extensions or may happen if you're installing/removing extensions from a remote container
You can install NPM-Scripts extension which does the same as npm scripts functionality which was build into vscode.
I am using VScode version 1.45 with Firefox version 76.0.1 as a default browser (with Ubuntu 18.04.4 LTS). Whenever I tried to open a link in the VSCode, it will open the Firefox browser under same icon as VSCode, and I cannot merge these tabs into existing Firefox web browser.
Same thing also happens when I try to run a program using live server extension. But when I use npm to start the development server, it will create a new window or tab under the Firefox icon.
How could I fix this so whenever I open a browser from VSCode, it will create a new browser or tab under the appropriate (Firefox) icon? Thank you.
There is already an issue on VSCode's GitHub repository and as it is mentioned in the issue, origin of the issue is in snapd.
To fix the issue, as mentioned on aforementioned github issue:
Open some URL from the VSCode snap.
In the new window, navigate to about:profiles.
Ensure that the profile marked as "Default Profile" matches Firefox when opened normally. If not, use the "Set as default profile" button under the correct profile to change the default.
Try making firefox your default browser thorugh firefox and also do check that firefox is your default browser from vscode
I found this solution the best solution
You might have installed VSCode as a snap package, which causes
$XDG_CACHE_HOME to be set to ~/snap/code/common/.cache, which could
cause some cli tools to mistake that for your cache directory, and
install/launch binaries from there.
If you install VSCode from the .deb download, it should fix your issue
I removed vscode from Ubuntu software and download the .deb file from vscode site and install it ... problem solved
I use the extension Latex Workshop, however my preview does not auto update on save. I have to run pdflatex each time.
I tried uninstalling and installing the extension, deleting the extensions file, and even reinstalled vs code. Yet, the same thing persists.
Is there a specific setting, etc that needs to be changed?
Strangely for me it only seems to work when configuring
latex-workshop.latex.autoBuild.run: "onSave"
As from here the setting for this is:
latex-workshop.latex.autoBuild.run
With value "onFileChange".
Note that this is the default value for this setting, so it should detect the changes automatically, but give it a try.
Local and ssh installation:
For me the problem was that I had Latex Workshop installed on SSH but not locally. After installing locally, the LaTEX icon showed up and also auto-compile on save worked right away.
Recently the dropdown menus in jupyter / ipython notebook have stopped working. I'm loathe to do a full anaconda reinstall without first understanding what's going wrong.
Hopefully this gif is sufficiently self explanatory of the problem. There's no error messages appearing that I can see in terminal. The other buttons in the header still work.
Updating jupyter did not work for me, however, disabling my pop-up blocker did the trick ('poper blocker' for Firefox in my case)
Running
conda update jupyter
seemed to the fix the problem somehow, even when reinstalling Anaconda did not.
I had a very similar issue, I could click on most of the menu items but just not the file menu. It wasn't an issue then one day it was. I deleted a chrome extension that I had: Kernel Hub, which I never used but was suppose to push kaggle updates to github, then I refreshed the page. I dunno if it was removing the extension up refreshing that fixed it but now it works.
For me it was a Chrome extension that caused the problem. I uninstalled it, reloaded the Jupyter Notebook page and the menus opened normally again.