Skip to content

chore: add debug information to wsproxy errors #9683

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 2 commits into from
Sep 20, 2023

Conversation

Emyrk
Copy link
Member

@Emyrk Emyrk commented Sep 14, 2023

Closes #8532

There is not enough information to solve the issue, and we do not have a reproducible environment. I added debugging information to the proxy page, and when the information is hard to display, I added debugging steps.

So this should provide more context if this resurfaces.

Screenshot from 2023-09-14 10-13-35

@Emyrk Emyrk merged commit f89b680 into main Sep 20, 2023
@Emyrk Emyrk deleted the stevenmasley/wsproxy_more_error_info branch September 20, 2023 15:05
@github-actions github-actions bot locked and limited conversation to collaborators Sep 20, 2023
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.

Running wsproxy not showing healthy in dashboard
2 participants