-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Markup cell initialize fail on window reload #161520
Labels
bug
Issue identified by VS Code Team member as probable bug
candidate
Issue identified as probable candidate for fixing in the next release
important
Issue identified as high-priority
insiders-released
Patch has been released in VS Code Insiders
notebook-markdown
verified
Verification succeeded
Milestone
Comments
rebornix
added
bug
Issue identified by VS Code Team member as probable bug
important
Issue identified as high-priority
notebook-markdown
labels
Sep 22, 2022
mjbvz
added a commit
to mjbvz/vscode
that referenced
this issue
Sep 23, 2022
- initializeMarkup should always fire `initializedMarkup`, even if an exception is thrown while initializing - `MarkupCell` should always resolve its `ready` property, even if an exception is thrown during rendering Unclear if either of these were the causes of microsoft#161520, but still good to fix them
mjbvz
added a commit
that referenced
this issue
Sep 23, 2022
- initializeMarkup should always fire `initializedMarkup`, even if an exception is thrown while initializing - `MarkupCell` should always resolve its `ready` property, even if an exception is thrown during rendering Unclear if either of these were the causes of #161520, but still good to fix them
Closing since we haven’t seen this happening again recently |
mjbvz
added
the
candidate
Issue identified as probable candidate for fixing in the next release
label
Sep 30, 2022
mjbvz
added a commit
to mjbvz/vscode
that referenced
this issue
Sep 30, 2022
This tries to fix microsoft#161520 by doing the following: - Wait for basic initialization to finish before posting messages - `initializedMarkup` should wait for the correct response instead of the first response This fixes the issue in my testing, but causes the layout to shift around during load
mjbvz
added a commit
that referenced
this issue
Oct 4, 2022
* Fix race when loading notebook webviews This tries to fix #161520 by doing the following: - Wait for basic initialization to finish before posting messages - `initializedMarkup` should wait for the correct response instead of the first response This fixes the issue in my testing, but causes the layout to shift around during load * wait for js preload to be initialized in webview * Removed pending message queue * Remove extra async Co-authored-by: rebornix <[email protected]>
vscodenpa
added
the
unreleased
Patch has not yet been released in VS Code Insiders
label
Oct 4, 2022
mjbvz
added a commit
to mjbvz/vscode
that referenced
this issue
Oct 4, 2022
* Fix race when loading notebook webviews This tries to fix microsoft#161520 by doing the following: - Wait for basic initialization to finish before posting messages - `initializedMarkup` should wait for the correct response instead of the first response This fixes the issue in my testing, but causes the layout to shift around during load * wait for js preload to be initialized in webview * Removed pending message queue * Remove extra async Co-authored-by: rebornix <[email protected]>
mjbvz
added a commit
that referenced
this issue
Oct 4, 2022
* Fix race when loading notebook webviews This tries to fix #161520 by doing the following: - Wait for basic initialization to finish before posting messages - `initializedMarkup` should wait for the correct response instead of the first response This fixes the issue in my testing, but causes the layout to shift around during load * wait for js preload to be initialized in webview * Removed pending message queue * Remove extra async Co-authored-by: rebornix <[email protected]> Co-authored-by: rebornix <[email protected]>
rzhao271
added
verified
Verification succeeded
and removed
verification-found
Issue verification failed
labels
Oct 5, 2022
vscodenpa
added
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 7, 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
candidate
Issue identified as probable candidate for fixing in the next release
important
Issue identified as high-priority
insiders-released
Patch has been released in VS Code Insiders
notebook-markdown
verified
Verification succeeded
This is hard to have stable reproduce but almost every one in the notebook v-team ran into this in last few weeks: when reloading the window with a notebook editor open, the notebook editor might not open successfully, closing it and reopening the same document can fix it.
Debugged with log points in Insiders and I found it failed in
BacklayerWebview#initializeMarkup
vscode/src/vs/workbench/contrib/notebook/browser/view/renderers/backLayerWebView.ts
Lines 1159 to 1182 in d847171
The
initializeMarkup
message is sent to the webview (at least we called the webviewpostMessage
) but the response never came back. When this happens, the webview/iframe contains thehtml
content, Jupyter notebook renderers' styles, but it doesn't have anything related to the markup renderers (no markup css).@mjbvz please help take a look, we can have a call to do some debugging together.
The text was updated successfully, but these errors were encountered: