Conversation
.vscode/launch.json
Outdated
| "skipFiles": [ | ||
| "<node_internals>/**" | ||
| ] | ||
| ], |
There was a problem hiding this comment.
I don't think we want this on all the time.
There was a problem hiding this comment.
Codecov Report
@@ Coverage Diff @@
## master #10115 +/- ##
=========================================
Coverage ? 61.31%
=========================================
Files ? 567
Lines ? 30704
Branches ? 4402
=========================================
Hits ? 18827
Misses ? 10894
Partials ? 983
Continue to review full report at Codecov.
|
| return response; | ||
| } catch (e) { | ||
| if (product === Product.jupyter) { | ||
| sendTelemetryEvent(Telemetry.JupyterInstallFailed); |
There was a problem hiding this comment.
Not relevant in particular to our team. But might be worthwhile just for the extension in general to log telemetry on UserModuleInstallFailed. #WontFix
There was a problem hiding this comment.
Dan/Savannah can ask for this if they want it I think. Not sure we should add telemetry unless they want it.
In reply to: 379120268 [](ancestors = 379120268)
| // Python Module to be used when instantiating the Python Daemon. | ||
| export const PythonDaemonModule = 'datascience.jupyter_daemon'; | ||
|
|
||
| export const KnownNotebookLanguages: string[] = [ |
There was a problem hiding this comment.
Just wondering where did these values come from. Didn't think that nbformat specified language specific language_info name values. #Resolved
There was a problem hiding this comment.
I looked them up in a bunch of notebooks on github.
In reply to: 379122367 [](ancestors = 379122367)
There was a problem hiding this comment.
Actually some of them are the wrong case though. I should check case insensitive.
In reply to: 379122816 [](ancestors = 379122816,379122367)
| this.applicationShell.showErrorMessage(e.message, DataScience.pythonInteractiveHelpLink()) | ||
| ); | ||
| .then(() => { | ||
| sendTelemetryEvent(Telemetry.UserInstalledModule, stopWatch.elapsedTime, { product }); |
There was a problem hiding this comment.
This is also a jupyter install looks like. #Resolved
There was a problem hiding this comment.
There was a problem hiding this comment.
Yeah, looks like just a non-Conda jupyter install. Not User Module. #Resolved
IanMatthewHuff
left a comment
There was a problem hiding this comment.
Approved pending a couple of comments
|
What were you waiting on? I think they're all fixed? In reply to: 358564725 [](ancestors = 358564725) |
@rchiodo at the time I clicked approve the UserModule message was not resolved (at least not that saw). Clicked approve with comment as I didn't care / need to see the review after that fix. Figured you could just check in after fixing that. |
|
Kudos, SonarCloud Quality Gate passed!
|
* Add duration to select local/remote kernel * Add notebook language telemetry * Add news entries * #9883 telemetry * News entry * Another spot for kernel spec failure * Add telemetry on product install * Fix install telemetry * Undo launch.json change * Handle other cases * Better way to handle case * Wrong event for jupyter install * Fix unit tests
* Better messaging on notebook fail (#10056) * Install jupyter instead of installing kernel spec (#10080) * Install jupyter instead of installing kernel spec For #10071 * Eliminate variable value when computing data frame info (#10081) * Fix ndarray types to be viewable again (#10093) * Eliminate variable value when computing data frame info * Fix ndarrays to work again Add test to make sure we don't regress this again * Rchiodo/kernel telemetry (#10115) * Add duration to select local/remote kernel * Add notebook language telemetry * Add news entries * #9883 telemetry * News entry * Another spot for kernel spec failure * Add telemetry on product install * Fix install telemetry * Undo launch.json change * Handle other cases * Better way to handle case * Wrong event for jupyter install * Fix unit tests * Clear variables when restarting regardless if visible or not (#10117) * Use different method for checking if kernelspec is available (#10114) * Use different method for checking if kernelspec is available * Fix unit tests * More logging for kernelspec problems (#10132) * More logging for kernelspec problems * Actually capture the exception on the new code * Not actually using output if first exception still there. * Actually only return output on one of the expected calls. * Fix nightly flake * Check our saved jupyter interpreters before allowing any of them to be used as active interpreters (#10113) * Update changelog and package.json * Missing part of changelog * Fix tests and linter problems Co-authored-by: Ian Huff <ian.huff@gmail.com> Co-authored-by: Don Jayamanne <don.jayamanne@yahoo.com>
For #10049, #9819, #9883
Add a bunch of telemetry:
And fix some others to have durations.