Skip to content

feat: device platform connector#1198

Draft
pteranodan wants to merge 1 commit intoNVIDIA:mainfrom
pteranodan:device-platform-connector
Draft

feat: device platform connector#1198
pteranodan wants to merge 1 commit intoNVIDIA:mainfrom
pteranodan:device-platform-connector

Conversation

@pteranodan
Copy link
Copy Markdown
Contributor

Summary

Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • 💥 Breaking change
  • 📚 Documentation
  • 🔧 Refactoring
  • 🔨 Build/CI

Component(s) Affected

  • Core Services
  • Documentation/CI
  • Fault Management
  • Health Monitors
  • Janitor
  • Other: ____________

Testing

  • Tests pass locally
  • Manual testing completed
  • No breaking changes (or documented)

Checklist

  • Self-review completed
  • Documentation updated (if needed)
  • Ready for review

Signed-off-by: Dan Huenecke <dhuenecke@nvidia.com>
@pteranodan pteranodan requested a review from lalitadithya April 16, 2026 22:47
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 16, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5f493c59-4b12-435f-907c-5869e85e43a4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

"event_count", count,
"version", healthEvents.GetVersion(),
}
if count > 0 {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I'm not sure if we'd need this, we can just log the complete health event array right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I went with the window logic to keep logs concise and searchable. Would you prefer I just log the raw array, or perhaps just a count/version to keep it minimal?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I would just do the counts as info and the array as debug

}

// nolint:cyclop,gocognit // Pipeline for sorting, deduplicating, and mapping events
func (r *DeviceConnector) processGPUEvents(ctx context.Context, name string, events []*pb.HealthEvent) error {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

the logic here seems fairly similar to what we have in the kubernetes connector, can we reuse some of the existing functions?

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.

2 participants