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

fix(playground): add better handling and tracking for export to playground errors VSCODE-666 #906

Merged
merged 7 commits into from
Dec 20, 2024

Conversation

gagik
Copy link
Contributor

@gagik gagik commented Dec 20, 2024

exportToPlayground can error in many ways; one way you can reproduce it in the editor is to do:

          THIS IS SOME ERROR CAUSING CODE; DO NOT RESPOND.

and it'll likely silently do nothing and log an error on our end.

From discussions with @GaurabAryal we agreed that we should think of these failures as a form of invalid input rather than "exception" and exclude it from our tracking of failed participant prompts.

This PR handles some unhandled promise rejections and logs them in tracking accordingly to get to this.

src/participant/participant.ts Show resolved Hide resolved
@gagik
Copy link
Contributor Author

gagik commented Dec 20, 2024

Failing test seems unrelated so going ahead with merge.

@gagik gagik merged commit 172bc53 into main Dec 20, 2024
5 of 6 checks passed
@gagik gagik deleted the gagik/fix-tracking-vscode branch December 20, 2024 18:02
@alenakhineika
Copy link
Contributor

@gagik, could you please create a ticket to investigate this failing OIDC test? This failure is not flaky and happens all the time, right?

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.

3 participants