Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Dispose webviewhost on panel load failure #13129

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

Merged

Conversation

IanMatthewHuff
Copy link
Member

For #13106

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
  • Title summarizes what is changing.
  • Has a news entry file (remember to thank yourself!).
  • Appropriate comments and documentation strings in the code.
  • Has sufficient logging.
  • Has telemetry for enhancements.
  • Unit tests & system/integration tests are added/updated.
  • Test plan is updated as appropriate.
  • package-lock.json has been regenerated by running npm install (if dependencies have changed).
  • The wiki is updated with any design decisions/details.

@IanMatthewHuff
Copy link
Member Author

Could continually repro this issue when trying to repro the save issue. Seems to be related to opening and closing a bunch of ipynbs when the extension is still in the act of loading. If it hits it could lock you out from ever being able to open up a file until vscode was closed down or reloaded.

The "webview was disposed message" can still pop up. That seems to be coming from vscode and given our move to the new notebook editor I don't believe it's worth tracking down the root vscode cause. My fix here just prevents the "locked" state. That state was when the webpanel failed to load the host still existed and thought that it had a valid panel. So if you tried to reopen the file it would just try use the same panel and continually fail with the previous load promise.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@codecov-commenter
Copy link

codecov-commenter commented Jul 23, 2020

Codecov Report

Merging #13129 into master will decrease coverage by 0.05%.
The diff coverage is 25.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #13129      +/-   ##
==========================================
- Coverage   59.79%   59.74%   -0.06%     
==========================================
  Files         671      671              
  Lines       36681    36694      +13     
  Branches     5158     5156       -2     
==========================================
- Hits        21933    21921      -12     
- Misses      13655    13680      +25     
  Partials     1093     1093              
Impacted Files Coverage Δ
src/client/common/application/types.ts 100.00% <ø> (ø)
...rc/client/common/application/webPanels/webPanel.ts 9.33% <8.00%> (+0.50%) ⬆️
src/client/datascience/webViewHost.ts 44.93% <85.71%> (-4.12%) ⬇️
src/client/common/utils/platform.ts 64.70% <0.00%> (-11.77%) ⬇️
src/client/datascience/crossProcessLock.ts 79.41% <0.00%> (-11.77%) ⬇️
src/client/linters/pydocstyle.ts 86.66% <0.00%> (-2.23%) ⬇️
src/client/datascience/debugLocationTracker.ts 76.56% <0.00%> (-1.57%) ⬇️
src/client/common/process/proc.ts 14.49% <0.00%> (-0.73%) ⬇️
src/client/datascience/jupyter/jupyterNotebook.ts 4.25% <0.00%> (-0.02%) ⬇️
... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f26d2dd...d2733bd. Read the comment docs.

@IanMatthewHuff IanMatthewHuff merged commit 4784cd8 into microsoft:master Jul 23, 2020
@IanMatthewHuff IanMatthewHuff deleted the dev/ianhu/panelLoadIssue branch July 24, 2020 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants