Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue with creating and opening .ipynb files #106547

Closed
arezaz opened this issue Sep 12, 2020 · 70 comments
Closed

issue with creating and opening .ipynb files #106547

arezaz opened this issue Sep 12, 2020 · 70 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority insiders-released Patch has been released in VS Code Insiders verified Verification succeeded

Comments

@arezaz
Copy link

arezaz commented Sep 12, 2020

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

I have an issue with creating/opening Jupiter notebook files (.ipynb).

Steps to Reproduce:

  1. Python: Create New Blank Jupiter Notebook
  2. this pops up: "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."

attaching a screenshot for more details.
image

I did not have this problem before in VSCode.

Does this issue occur when all extensions are disabled?: Yes

@DominguesPH
Copy link

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.

@rahul-raj
Copy link

I have same problem as well!

@FuriouStyles
Copy link

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!

@DiaAzul
Copy link

DiaAzul commented Sep 12, 2020

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.

@SharoonSaxena
Copy link

SharoonSaxena commented Sep 12, 2020

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. :-[]

@Sricharan2402
Copy link

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

@rahul-raj
Copy link

image
Attaching screenshot for reference.

@RSalu
Copy link

RSalu commented Sep 12, 2020

me too I have the same problem.

@arezaz
Copy link
Author

arezaz commented Sep 12, 2020

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

@DominguesPH
Copy link

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

@Meet19aug
Copy link

i also did it but still facing same problem .

@edinsonAC
Copy link

some solution?

@dshot92
Copy link

dshot92 commented Sep 12, 2020

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

image

@Rajwantmishra
Copy link

Same problem,

@Rajwantmishra
Copy link

Rajwantmishra commented Sep 13, 2020

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?

@Meet19aug
Copy link

Capture
still facing issue

@jfbldevs
Copy link

Same problem

@calbertrov
Copy link

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.

@ghost
Copy link

ghost commented Sep 13, 2020

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

@calbertrov
Copy link

calbertrov commented Sep 13, 2020

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

@rahul-raj
Copy link

rahul-raj commented Sep 13, 2020

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

@fuzzyudo
Copy link

fuzzyudo commented Sep 13, 2020

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!

@shashwatk1
Copy link

Just uninstalled everything and then reinstalled everything, problem still persists

@RSalu
Copy link

RSalu commented Sep 13, 2020

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.

@mcaires2
Copy link

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.

@RSalu
Copy link

RSalu commented Sep 13, 2020

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

@Meet19aug
Copy link

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

@Loligplayer33
Copy link

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

@mjbvz
Copy link
Collaborator

mjbvz commented Sep 14, 2020

@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?

@rchiodo
Copy link
Contributor

rchiodo commented Sep 14, 2020

@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.

@rchiodo
Copy link
Contributor

rchiodo commented Sep 14, 2020

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

@rebornix
Copy link
Member

@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.

@rchiodo
Copy link
Contributor

rchiodo commented Sep 14, 2020

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).

@rebornix
Copy link
Member

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.

@DiaAzul
Copy link

DiaAzul commented Sep 14, 2020

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

@mjbvz
Copy link
Collaborator

mjbvz commented Sep 14, 2020

@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

@mjbvz mjbvz removed the candidate Issue identified as probable candidate for fixing in the next release label Sep 14, 2020
@rchiodo
Copy link
Contributor

rchiodo commented Sep 14, 2020

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

@rchiodo
Copy link
Contributor

rchiodo commented Sep 14, 2020

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

@rchiodo
Copy link
Contributor

rchiodo commented Sep 14, 2020

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

@anupampydey
Copy link

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.

@rchiodo
Copy link
Contributor

rchiodo commented Sep 15, 2020

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

@Jill-Cheng
Copy link

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

@mjbvz mjbvz closed this as completed in af5dd22 Sep 17, 2020
@mjbvz
Copy link
Collaborator

mjbvz commented Sep 17, 2020

@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

@songpr
Copy link

songpr commented Sep 17, 2020

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

@rchiodo
Copy link
Contributor

rchiodo commented Sep 17, 2020

@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"
    ],
  1. Open a python file
  2. 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.
  3. 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.

@rchiodo
Copy link
Contributor

rchiodo commented Sep 17, 2020

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

@songpr
Copy link

songpr commented Sep 18, 2020

@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.

@rchiodo
Copy link
Contributor

rchiodo commented Sep 18, 2020

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"
    ],

@songpr
Copy link

songpr commented Sep 20, 2020

image
@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

@jrieken jrieken added the verified Verification succeeded label Oct 1, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Nov 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Development

No branches or pull requests