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

Cannot open notebook in vscode.dev, error reading property message #164715

Closed
lramos15 opened this issue Oct 26, 2022 · 5 comments
Closed

Cannot open notebook in vscode.dev, error reading property message #164715

lramos15 opened this issue Oct 26, 2022 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders notebook-serialization verified Verification succeeded
Milestone

Comments

@lramos15
Copy link
Member

lramos15 commented Oct 26, 2022

Started up insiders.vscode.dev for the first time in awhile and received the following error

image

Seems to come from here.

const error = createErrorWithActions(e instanceof Error ? e : new Error(e.message), [
toAction({

This only repros when I use the endgame vscode.dev query provided. Opening the file myself seems to work

@rebornix
Copy link
Member

@lramos15 do you see this every time when opening the link? It seems that it throws with an undefined error but we failed to read the error message. It didn't explain why the file opening fails though.

@rebornix rebornix added the bug Issue identified by VS Code Team member as probable bug label Oct 26, 2022
@rebornix rebornix added this to the October 2022 milestone Oct 26, 2022
@lramos15
Copy link
Member Author

@lramos15 do you see this every time when opening the link? It seems that it throws with an undefined error but we failed to read the error message. It didn't explain why the file opening fails though.

I see it every time. I can try again tomorrow when this change goes in to see if there is a more detailed error message.

@joyceerhl
Copy link
Contributor

I just hit this as well twice @rebornix but third time didn't repro

@rebornix rebornix reopened this Oct 26, 2022
@joyceerhl
Copy link
Contributor

joyceerhl commented Oct 26, 2022

This will fail
https://insiders.vscode.dev/github/microsoft/vscode/blob/9f5d3eb1353f6e6bd5ab7bccab9d50b0aba15209/.vscode/notebooks/endgame.github-issues#C22:L1

This is OK
https://insiders.vscode.dev/github/microsoft/vscode/blob/9f5d3eb1353f6e6bd5ab7bccab9d50b0aba15209/.vscode/notebooks/endgame.github-issues#C23:L1

We think it's because C22 is a markdown cell and C23 is a code cell

How it looks: the editor progress bar spins forever, when you start scrolling the error modal dialog pops up
It's quite possible this was always there but is more visible now that we're using vscode.dev notebook cell deeplinks

@rebornix
Copy link
Member

rebornix commented Oct 26, 2022

I prepared a fix for this one, by turning the cell into editing mode if there is a selection in the link #164758. If we drop L1 from the link, you can find it open successfully.

However currently whenever we copy a link from a markdown cell preview, we always append L1 ion the link, we should probably only append line number when the cell is in editing mode, tracked in https://github.com/microsoft/vscode-dev/issues/749

@vscodenpa vscodenpa added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Oct 26, 2022
formigoni pushed a commit to formigoni/vscode that referenced this issue Oct 27, 2022
@lramos15 lramos15 added the verified Verification succeeded label Oct 27, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Dec 10, 2022
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 insiders-released Patch has been released in VS Code Insiders notebook-serialization verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants