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

Ignore load err that stops Python Ext from loading #5146

Merged
merged 5 commits into from
Mar 17, 2021
Merged

Conversation

DonJayamanne
Copy link
Contributor

For #5145

@DonJayamanne DonJayamanne requested a review from a team as a code owner March 12, 2021 21:06
@@ -58,7 +60,19 @@ export async function activate(context: IExtensionContext): Promise<IExtensionAp
// We want to completely handle the error
// before notifying VS Code.
await handleError(ex, durations);
throw ex; // re-raise
traceError('Failed to active the Jupyter Extension', ex);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pro this, as I'm big on not busting python. But just to ask. Does this make an odd customer case if they just have Jupyter installed? Like it just fails for the user without visual notification? Wondering about either only doing this if Python is installed or popping up a message (I'm assuming that the re-raise is what would usually show the message) so that the user at least knows what happened.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

uming that the re-raise is what would usually show the message) so that the user at least knows what happened.

I think its just to tell VS Code we failed.

await handleError(ex, durations);

this is where a message is displayed to the user today.
So if the extension fails to load they'll see a message (exiting code)

@codecov-io
Copy link

codecov-io commented Mar 16, 2021

Codecov Report

Merging #5146 (aff61c3) into main (3d558a3) will increase coverage by 2%.
The diff coverage is 41%.

❗ Current head aff61c3 differs from pull request most recent head 07e17a1. Consider uploading reports for the commit 07e17a1 to get more accurate results

@@          Coverage Diff           @@
##            main   #5146    +/-   ##
======================================
+ Coverage     71%     73%    +2%     
======================================
  Files        402     402            
  Lines      26392   26403    +11     
  Branches    3798    3799     +1     
======================================
+ Hits       18741   19446   +705     
+ Misses      6091    5478   -613     
+ Partials    1560    1479    -81     
Impacted Files Coverage Δ
src/client/extension.ts 58% <41%> (-6%) ⬇️
.../client/datascience/notebook/kernelWithMetadata.ts 83% <0%> (-4%) ⬇️
src/client/common/configuration/service.ts 82% <0%> (ø)
src/client/datascience/liveshare/liveshare.ts 75% <0%> (ø)
src/client/common/application/encryptedStorage.ts 57% <0%> (ø)
src/client/datascience/jupyter/serverUriStorage.ts 87% <0%> (ø)
...lient/datascience/jupyter/kernels/cellExecution.ts 77% <0%> (ø)
src/client/datascience/notebook/helpers/helpers.ts 76% <0%> (+<1%) ⬆️
...active-common/intellisense/intellisenseProvider.ts 74% <0%> (+<1%) ⬆️
...ient/datascience/editor-integration/codewatcher.ts 69% <0%> (+<1%) ⬆️
... and 98 more

@DonJayamanne DonJayamanne merged commit d99989e into main Mar 17, 2021
@DonJayamanne DonJayamanne deleted the disableFailures branch March 17, 2021 17:01
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.

5 participants