Same:

• VSCode Version: 1.49.0
• OS Version: Windows_NT x64 10.0.18363

I'm having the same problem!
It started after I update the VS code version form 1.48 to 1.49.
I just made a plot, closed the window and when returned, this error appeared.
Also, when I try to open saved jupyter notebooks, it don't stop loading.

I have same problem as well!

I don't know if it's related, but I can't open an existing notebook either. I tried creating a new one just to see what would happen and this error popped up!

Unable to open any Python Jupyter Notebooks (.ipynb) following upgrade to VSCode Version: 1.49.0

When trying to open a notebook there is a cylon progress bar circulating at the top of the frame with the notebook name, however, no notebook contents. Doesn't appear to time out.

The problem manifested when I switched to a different project/workspace, up until that point I was able to open notebooks under 1.49.0 in the project I was working on prior to the upgrade without problem.

I am having similar issue! Updated to 1.49.0 and the notebook simply keeps loading the ipynb file without any response.
Tried uninstalling and reinstalling the older 1.48.2 version. Still the same problem. Notebook simply keeps loading.
Screenshot:
the notebook doesn't timeout
Unfortunately this happened during a presentation. :-[]

Same problem here.
Tried using vscode-insiders, didn't work either.

Attaching screenshot for reference.

me too I have the same problem.

I did this and was able to pull up a Jupyter notebook in the VSCode insider release:
(not sure what the logic is!)

1. uninstall VSCode
2. press win + R, type in %appdata%
3. find the Code folder and delete it
4. install the VSCode Insider

I did this and was able to pull up a Jupyter notebook in the VSCode insider release:
(not sure what the logic is!)

1. uninstall VSCode
2. press win + R, type in %appdata%
3. find the Code folder and delete it
4. install the VSCode Insider

I did the same, the problem persists

i also did it but still facing same problem .

some solution?

Same problem Here as well.
I was actually a version earsling of the 1.49.
I updated hoping that was it.

No luck.
Tried a fresh install but it doesn't work either.

Error:
Unable to open 'Untitled-1.ipynb': [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character.

It won't even load the cells

Same problem,

I download only insider (https://code.visualstudio.com/insiders/) and python extension, but now I have a different VS code (VS Insider ) that works.

Is VS Code being replaced by VS insider?

still facing issue

Same problem

I have the same issue on one system which uses version 3.8.5, but the version 3.8.2 works on my other system works.

I am facing the same issue. With the latest vscode version.

Spoke toooo Soon... Still locked out of Jupyter NB

My vscode version is 1.49 and I'm still having the issue.
No one from the vscode team checked this issue yet.

Have got the same Problem on a machine with W10, Python 3.8.5, VSC 1.49.0 and Python extension v2020.8.108011.
On a different machine I have no problems: W10, Python 3.7.0, VSC 1.49.0 and Python extension v2020v8v108011.
It seems to be an issue of the combination of versions of VSC and python.

Update:
On that machine, on that I had no problems, I installed python 3.8.5, created a virutal environment with pipenv and was able to use "Python: Create New Blank Jupyter Notebook" without any problem.
Crazy!

Just uninstalled everything and then reinstalled everything, problem still persists

after resetting completly my Python installation and make a fresh install of anaconda, the problem still persist.
Notebook doesn't run under VS Code! On the other side Anaconda Notebook run perfectly without issue.
The issue is by VS Code, I hope MS will corect this next week.

The same problem here. What's happening? Is there a way to solve?

Unable to open 'Untitled-2.ipynb': [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character.

I've just installed the insider Version: [https://code.visualstudio.com/insiders/]. It's work fine

@RSalu can see the screenshot which i have shared in these conversation is from vscode insider but still facing same issue

What i think is strange that it works for me on windows but not on linux...

@jrieken That looks like a bug on the VS Code side but people also are reporting this in 1.48 and we haven't touched that code recently

@joyceerhl or someone from the Python team: was there a new python release that enabled new functionality that trigged this bug (such as the release on the 9th)? Also this may be related to an experiment. Is there a way to force the extension into the broken state?

@mjbvz yes I believe it was a change to our experiments that might have caused it.

You can set this in your user settings.json to repro I believe:

    "python.experiments.optInto": [
        "CustomEditorSupport - experiment"
    ],

That experiment was enabled on Friday by mistake.

Also explains why not everybody is hitting this. That experiment turns on our usage of the custom editor API.

@rchiodo I can reproduce with experiment optInfo posted above, is there any way for me to opt out after adding that setting? I removed it but it still tries to ope with custom editor.

Turning off that setting is supposed to opt out, but if that doesn't work you might also have to remove the python extension and reinstall it.

Turning on that setting modifies the python package's package.json on disk (or at least it used to).

Thanks, removing the optInfo and uninstalling the extension then re-install fixes this problem. It can be a workaround recommended to users before we ship the recovery build.

Thanks, removing the optInfo and uninstalling the extension then re-install fixes this problem. It can be a workaround recommended to users before we ship the recovery build.

Confirmed works

@rchiodo Can you please revert the experiment change on the Python side? Again, while there does seem to be a bug on the VS Code side, it does not appear to be a VS Code regression. I'd prefer avoiding the risk of a patch fix in VS Code 1.49. Better to fix this in insiders so we get additional testing before it goes out with 1.50

That requires us to ship a fix then too (as it doesn't seem that undoing the experiment is enough - experiment is actually downloaded from github on startup). Our next shipping date should be a week from today

Or we can try and fix a patch release just to fix the bug where the experiment requires a reinstall.

Actually just revving the version number should fix the problem. That should be easier to get out.

I too faced the URIError day before yesterday. The jupyter notebooks won't open in VS code. Wasted considerable time in uninstalling the current version and reinstalling the older version but the error persisted. Today I updated by windows 10 and problem has gone automatically. Don't know what happened but now with VS Code I can open both saved notebooks and new notebooks.

Python extension released a new version. That should alleviate the problem for most people.

@rchiodo It works for me when I use the latest version of python extension (2020.8.109390), thank you!

@rchiodo I pushed a fix into VS Code insiders. However I still don't see the Python custom editor successfully loading after pushing this (it looks like it never resolves). I also can't get it working on MacOS using VS Code 1.49, so this may be an issue with the custom editor implementation.

Please test out the next insiders build and let me know if you think something is off on the VS Code side

I have try the insider release, however the .ipynb is still show as blank

@mjbvz the latest insider's build still repros the problem. To repro:

1. Install python extension (not the insiders version of this as the insiders is disabling custom editor at the moment)
2. Set this in your global user settings:

    "python.experiments.optInto": [
        "CustomEditorSupport - experiment"
    ],

3. Open a python file
4. Reload VS code when it asks (if it doesn't, do it manually). This step is necessary because enabling the custom editor experiment will rewrite our package.json.
5. Try opening a notebook.

You should end up with the screen like @songpr had. If you run Toggle Maximize Panel and reopen the notebook, it will open correctly.

However the other bug - creating a new blank notebook, that has been fixed. The notebook just hits the same problem where you have to maximize the panel first.

The blank ipynb is really this issue here (which for us is more important than fixing the URI problem).
#106673

@rchiodo so you mean if I turn off custom editor it will work right?

Could you let me know how to do it I search the setting but cannot found the option that you show.

Custom editor is an opt in only scenario at the moment.

We accidentally enabled it for 20% of users on the 11th. If you reinstall the python extension it should go back to not being enabled.

If that still doesn't work, double check this value isn't set in your settings.json:

    "python.experiments.optInto": [
        "CustomEditorSupport - experiment"
    ],

@rchiodo the value is not in setting.json.
However the jupyter file still cannot open

Updated 21 Sep 2020.
Finally, it work now.
Python 2020.8.109390
VS Code 1.49.1