Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: do not fail DERP healthcheck if WebSocket is used#10714

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
mtojek merged 12 commits intomainfrom9470-warnings
Nov 17, 2023

Conversation

mtojek
Copy link
Member

@mtojekmtojek commentedNov 15, 2023
edited
Loading

Fixes:#9470
Replaces:#10620

This PR extends the/api/v2/debug/health API response to includewarning []string field. Also, Coder will not report "unhealthy" status if there are troubles with Websockets.

Screenshot 2023-11-17 at 14 44 52

@mtojekmtojek self-assigned thisNov 15, 2023
@mtojekmtojek marked this pull request as ready for reviewNovember 17, 2023 14:18
// @typescript-generate Report
type Report struct {
Healthy bool `json:"healthy"`
Healthy bool `json:"healthy"`
Warnings []string `json:"warnings"`
Copy link
Member

Choose a reason for hiding this comment

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

Should this be amap[string][]string so that it's easier to identify the source of the warnings?

That way we don't need to worry about doingfmt.Sprintf("[%s] %s", prefix, warning") all the time.

Copy link
Member

Choose a reason for hiding this comment

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

It might also make easier for the UI to display them separately.

Copy link
MemberAuthor

@mtojekmtojekNov 17, 2023
edited
Loading

Choose a reason for hiding this comment

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

I don't have a strong preference here, but[]string is convenient as it is defined the same way for every section. Frontend can just render all warnings as is. If you find it useful, I can just adjust the implementation though.

Copy link
MemberAuthor

@mtojekmtojekNov 17, 2023
edited
Loading

Choose a reason for hiding this comment

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

It might also make easier for the UI to display them separately.

My main concern is consistency with otherwarnings []string fields, but I don't mind changing it.

Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure what would be easier for the UI, to be honest. Maybe we just ship and iterate?

mtojek reacted with thumbs up emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Agree 👍

@mtojekmtojek merged commit8999d57 intomainNov 17, 2023
@mtojekmtojek deleted the 9470-warnings branchNovember 17, 2023 15:00
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsNov 17, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@johnstcnjohnstcnjohnstcn approved these changes

@BrunoQuaresmaBrunoQuaresmaAwaiting requested review from BrunoQuaresma

Assignees

@mtojekmtojek

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

health check endpoint: do not showhealthy: false if Coder falls back to websockets
2 participants
@mtojek@johnstcn

[8]ページ先頭

©2009-2025 Movatter.jp