8000 feat: CollectDiagnosticData by joeyberkovitz · Pull Request #2 · coreweave/gofish · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: CollectDiagnosticData #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and 8000 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 22 commits into from
Jun 17, 2025
Merged

feat: CollectDiagnosticData #2

merged 22 commits into from
Jun 17, 2025

Conversation

joeyberkovitz
Copy link

add support for CollectDiagnosticData

fixes https://coreweave.atlassian.net/browse/METALDEV-937

mwieczorek and others added 11 commits March 7, 2025 08:02
…tmcginnis#419)

* common: Extract common http patch/post code into separate functions

* Refactor VirtualMedia.InsertMedia to call InsertMediaConfig

No need for similar implementations when InsertMedia is basically a
specialization of InsertMediaConfig.

* virtualmedia: Return Tasks if present in InsertMedia http response
* Bump golangci/golangci-lint-action from 6 to 8

Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 6 to 8.
- [Release notes](https://github.com/golangci/golangci-lint-action/releases)
- [Commits](golangci/golangci-lint-action@v6...v8)

---
updated-dependencies:
- dependency-name: golangci/golangci-lint-action
  dependency-version: '8'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update golangci-lint to v2.1.6

Updates the linter and fixes the few issues found.

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Sean McGinnis <sean.mcginnis@gmail.com>
…mcginnis#424)

This commit *adds* more SMC entity field names that should be allowed for read/write.
This started as matching the field names provided in
https://www.supermicro.com/manuals/other/redfish-ref-guide-html/Content/general-content/bmc-configuration-examples.htm
but then continued to follow the JSON field names that were found higher in each file
as that matched what a new SMC chassis expected.

The previous field names were left as read/write field names in case some of the older chassis BMCs
expect those names.

The NTP and Syslog file changes have been confirmed to fix bugs that we've seen
on our end. All of the changes are additions rather than updates/renames, so this should
break nothing.
Update payload logic was not aware of things like ",omitempty". This
would cause an invalid field name in the PATCH payload to update objects
with optional fields. This updates the handling to strip out this string
from the JSON property name.

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
@joeyberkovitz joeyberkovitz self-assigned this Jun 16, 2025
@joeyberkovitz joeyberkovitz requested a review from smiller248 June 16, 2025 18:57
iamsli
iamsli previously approved these changes Jun 16, 2025
update_gofish.sh Outdated
@@ -37,6 +45,6 @@ else
fi

# Merge back into main
git checkout main
git checkout "$PR_BRANCH_NAME"
Copy link
Collaborator

Choose a reason for hiding this comment

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

which remote is this checking out? this should be getting a fresh copy of upstream/main and then applying our patch on top of that, then pushing to internal/PR_BRANCH_NAME.

Copy link
Author

Choose a reason for hiding this comment

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

is it wrong as-is now?

so:

  • line 30: checkout main (should be origin AKA internal main)
  • 31: create the PR branch locally
  • fetch upstream and rebase it onto the PR branch
  • still on PR branch
  • 37: create a new apply branch to apply our patch
  • 48: come back to our local PR branch (already rebased onto upstream)
  • merge the patch back in again

the logic in the script was a bit confusing to me, but AFAIK, the only thing I changed was instead of rebasing origin/main we rebase $PR_BRANCH and then push that up to origin/$PR_BRANCH

Copy link
Collaborator

Choose a reason for hiding this comment

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

i think thats right. perhaps if we renamed the remotes to upstream and internal, it might make its more clear/explicit

@joeyberkovitz joeyberkovitz force-pushed the feat/collect-diagnostic branch from 05ebad9 to fff6384 Compare June 17, 2025 13:03
jplimack
jplimack previously approved these changes Jun 17, 2025
@joeyberkovitz joeyberkovitz dismissed jplimack’s stale review June 17, 2025 13:44

The merge-base changed after approval.

@joeyberkovitz joeyberkovitz merged commit 5a2b267 into main Jun 17, 2025
2 checks passed
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.

7 participants
0