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

fix(coderd/healthcheck): add daemon-specific warnings to healthcheck output#11490

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
johnstcn merged 2 commits intomainfromcj/provisioner-healthcheck-fixes
Jan 8, 2024

Conversation

johnstcn
Copy link
Member

@johnstcnjohnstcn commentedJan 8, 2024
edited
Loading

Follow-up to#11393
Part of#10676

  • Sorts provisioner daemons by name ascending in output
  • Adds daemon-specific warnings to healthcheck output
  • Reword some messages

- Sorts provisioner daemons by name ascending in output- Adds daemon-specific warnings to healthcheck output- Reword some messages
@johnstcnjohnstcn self-assigned thisJan 8, 2024
@johnstcnjohnstcn changed the titlefix(coderd/healthcheck): scope warnings in ProvisionerDaemonsReportfix(coderd/healthcheck): sort provisioner daemons by name in ProvisionerDaemonsReportJan 8, 2024
Copy link
Member

@mtojekmtojek left a comment

Choose a reason for hiding this comment

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

Left a few comments to address/respond to. Otherwise, it is 👍

Error*string`json:"error"`

ProvisionerDaemons []codersdk.ProvisionerDaemon`json:"provisioner_daemons"`
Items []ProvisionerDaemonsReportItem`json:"items"`
Copy link
Member

Choose a reason for hiding this comment

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

In theory, this is API breaking, right?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Yeah in theory, but the modifications were only merged this morning :-)


// Ensure stable order for display and for tests
sort.Slice(daemons,func(i,jint)bool {
returndaemons[i].Name<daemons[j].Name
Copy link
Member

Choose a reason for hiding this comment

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

doublecheck: we don't need to sort by other fields? There is no way that the report will contain old entries for provisioners with the same name?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

The database schema requires each provisioner daemon to have a unique name.

@johnstcnjohnstcn changed the titlefix(coderd/healthcheck): sort provisioner daemons by name in ProvisionerDaemonsReportfix(coderd/healthcheck): add daemon-specific warnings to healthcheck outputJan 8, 2024
@johnstcnjohnstcn merged commit93cf5dc intomainJan 8, 2024
@johnstcnjohnstcn deleted the cj/provisioner-healthcheck-fixes branchJanuary 8, 2024 13:55
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJan 8, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@mafredrimafredrimafredri approved these changes

@mtojekmtojekmtojek approved these changes

Assignees

@johnstcnjohnstcn

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@johnstcn@mafredri@mtojek

[8]ページ先頭

©2009-2025 Movatter.jp