Skip to content

refactor: setup errorTelemetry from electron-main #244020

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
merged 1 commit into from
Mar 20, 2025

Conversation

deepak1556
Copy link
Collaborator

Needed for #241390

Currently errors from electron-main are sent to the focused window via vscode:reportError channel to forward them to error telemetry. However, we also would like to send error telemetry for unresponsive windows in which case we need the capability to send telemetry from main process.

@deepak1556 deepak1556 added this to the March 2025 milestone Mar 19, 2025
@deepak1556 deepak1556 requested a review from bpasero March 19, 2025 16:57
@deepak1556 deepak1556 self-assigned this Mar 19, 2025
Copy link
Member

@bpasero bpasero left a comment

Choose a reason for hiding this comment

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

This is reasonable and I wonder why we never did this before (cc @lramos15) maybe just an oversight.

The one disadvantage this brings is that exceptions in the main process are not really visible anymore to devs because we mainly have the renderer dev console visible, though maybe with F5 debugging this changed anyway.

@deepak1556
Copy link
Collaborator Author

Will merge in its current state and follow-up based on feedback.

@deepak1556 deepak1556 merged commit 8dd2ad6 into main Mar 20, 2025
8 checks passed
@deepak1556 deepak1556 deleted the robo/add_error_telemetry_main branch March 20, 2025 03:10
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators May 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants