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.

Sign up for GitHub

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

Jump to bottom

Telemetry for window.newWindowProfile and extensions.autoRestart setting changes are getting reported using different event #219336

Closed
sandy081 opened this issue Jul 1, 2024 · 0 comments · Fixed by #219553
Closed

Telemetry for window.newWindowProfile and extensions.autoRestart setting changes are getting reported using different event #219336

sandy081 opened this issue Jul 1, 2024 · 0 comments · Fixed by #219553
Assignees
@sandy081
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Milestone
June 2024

Comments

@sandy081
Copy link
Member

sandy081 commented Jul 1, 2024

Steps to Reproduce:

  1. Enable Log Level to Trace and Open Telemetry Output view
  2. Change the value of window.newWindowProfile or extensions.autoRestart setting

🐛 These changes are being reported using window.systemColorTheme event.
@sandy081 sandy081 added bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release labels Jul 1, 2024
@sandy081 sandy081 added this to the June 2024 milestone Jul 1, 2024
@sandy081 sandy081 self-assigned this Jul 1, 2024
@sandy081 sandy081 changed the title Fix reporting telemetry for window.newWindowProfile and extensions.autoRestart settings Telemetry for window.newWindowProfile and extensions.autoRestart setting changes are getting reported using different event Jul 1, 2024
sandy081 added a commit that referenced this issue Jul 1, 2024
@sandy081
fix #219336
3467f94
@sandy081 sandy081 mentioned this issue Jul 1, 2024
Merged
benibenj pushed a commit that referenced this issue Jul 1, 2024
@sandy081
fix #219336 (#219337)
ea1445c 
* fix #219336

* fix owner
sandy081 added a commit that referenced this issue Jul 1, 2024
@sandy081
fix #219336 (#219337)
a76f9ca 
* fix #219336

* fix owner
@sandy081 sandy081 mentioned this issue Jul 1, 2024
Merged
@vscodenpa vscodenpa added the unreleased Patch has not yet been released in VS Code Insiders label Jul 1, 2024
@vscodenpa 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 Jul 3, 2024
aaronchucarroll pushed a commit to aaronchucarroll/vscode that referenced this issue Jul 10, 2024
@sandy081 @aaronchucarroll
fix microsoft#219336 (microsoft#219553)
09c3642 
fix microsoft#219336 (microsoft#219337)

* fix microsoft#219336

* fix owner
@rzhao271 rzhao271 added the verified Verification succeeded label Jul 25, 2024
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Aug 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sandy081 sandy081

Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Milestone
June 2024
Development

Successfully merging a pull request may close this issue.

fix #219336 microsoft/vscode
3 participants
@rzhao271 @sandy081 @vscodenpa