Use vscode-extension-telemetry for our exceptions & error telemetry #11524
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(update when getInterpreters signature change gets merged)
kimadeline
requested review from
karrtikr and
karthiknadig
and removed request for
karthiknadig and
karrtikr
|
Kudos, SonarCloud Quality Gate passed!
|
Codecov Report
@@ Coverage Diff @@
## master #11524 +/- ##
==========================================
- Coverage 60.49% 60.41% -0.08%
==========================================
Files 618 618
Lines 33750 33750
Branches 4760 4759 -1
==========================================
- Hits 20418 20391 -27
- Misses 12323 12351 +28
+ Partials 1009 1008 -1
Continue to review full report at Codecov.
|
karthiknadig
approved these changes
May 3, 2020
karrtikr
approved these changes
May 4, 2020
karrtikr
approved these changes
May 4, 2020
kimadeline
added a commit
to kimadeline/vscode-python
that referenced
this pull request
May 5, 2020
…emetry (microsoft#11524)" This reverts commit d5065e6.
10 tasks
kimadeline
added a commit
to kimadeline/vscode-python
that referenced
this pull request
May 6, 2020
…11602) * Revert "Fix slashes in telemetry unit tests (microsoft#11572)" This reverts commit 7431c9c. * Revert "Use vscode-extension-telemetry for our exceptions & error telemetry (microsoft#11524)" This reverts commit d5065e6. * Remove from changelog
karthiknadig
added a commit
that referenced
this pull request
May 19, 2020
* Revert vscode-extension-telemetry changes for the release (#11602) (#11656) * Revert "Fix slashes in telemetry unit tests (#11572)" This reverts commit 7431c9c. * Revert "Use vscode-extension-telemetry for our exceptions & error telemetry (#11524)" This reverts commit d5065e6. * Remove from changelog * Port storage fix to release branch (#11673) * Fix storage not being used (#11649) * Fix storage not being used * Add disposable to storage so it won't write after shutdown * Fix dirty title * Hack to get tests to pass * Another way to get run all to not interfere * Update changelog * Port scrolling fix to release (#11688) * Fix scrolling (#11681) * Fix scrolling * Review feedback - fix scrolling on expand/collapse * Update changelog * Update package.json Co-authored-by: Jim Griesmer <[email protected]> * Cherry-pick pipenv changes and pythonpath prompt changes to release (#11700) * Show the prompt again if user clicks on more info (#11664) * Show the prompt again if user clicks on more info * Review feedback * Use Learn more as text for the link. * Leave pipenv in a corner until the user decides to select an interpreter (#11654) * add onSuggestion option * Swap onActivation with onSuggestion * Update unit tests * Remove registration of IPipenvService * Move didTriggerInterpreterSuggestions logic inside pipenv locator * Fix existing unit tests * Add new unit tests * Replace typemoq any param with object * Shorten the tests * Fix warning * Duplicate teardown Co-authored-by: Kim-Adeline Miguel <[email protected]> * Update extension version (#11730) * Update extension version * Update date in changelog. * Update change log with additional notes. (#11764) * Cherry picks and version updates for bug fix release (#11878) * Do not execute shebang as an interpreter until user has clicked on the codelens enclosing the shebang (#11816) * Do not execute shebang as an interpreter until user has clicked on the codelens enclosing the shebang * Rename * Oops * Update src/test/providers/shebangCodeLenseProvider.unit.test.ts Co-authored-by: Karthik Nadig <[email protected]> Co-authored-by: Karthik Nadig <[email protected]> * Update version and change log for bugfix release Co-authored-by: Kartik Raj <[email protected]> * Clean up news Co-authored-by: Kim-Adeline Miguel <[email protected]> Co-authored-by: Rich Chiodo <[email protected]> Co-authored-by: Jim Griesmer <[email protected]> Co-authored-by: Kartik Raj <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #11436
👉 As discussed during standup, we will only send 1 telemetry event when there's an exception from now on, aka for an event of name 'foo' with custom props:
ERRORevent with the following props: stack trace and original event namefoo, no custom propsfoowith the custom propsnow we only will have:
ERRORevent with the following props: stack trace and original event namefoo, no custom props👉 Warnings are dismissed during packaging because they are not important: microsoft/vscode-extension-telemetry#41
Also, I packaged the extension and tried it locally, it still works (activation works, telemetry events are sent, tried selecting a linter, and when throwing an error then an
ERRORevent is sent)package-lock.jsonhas been regenerated by runningnpm install(if dependencies have changed).