ClusterCockpit/cc-backend
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-backend synced 2026-01-15 17:21:46 +01:00
Code Issues Packages Releases Activity

Mismatched event types are not something to be concerned about

Browse Source 
If a different CCMessage type was sent over the same subject as
requested, that shouldn't raise a warning. This may happen in production
instances, but in order to ease debugging, lower it to 'debug' level.
This commit is contained in:
Michael Panzlaff
2026-01-14 16:06:35 +01:00
parent d8cd752dcb
commit 94b86ef11a
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
internal/api/nats.go
View File

@@ -152,14 +152,14 @@ func (api *NatsAPI) handleJobEvent(subject string, data []byte) {
} }
if !m.IsEvent() { if !m.IsEvent() {
cclog.Warnf("NATS %s: received non-event message, skipping", subject) cclog.Debugf("NATS %s: received non-event message, skipping", subject)
continue continue
} }
if m.Name() == "job" { if m.Name() == "job" {
api.processJobEvent(m) api.processJobEvent(m)
} else { } else {
cclog.Warnf("NATS %s: unexpected measurement name '%s', expected 'job'", subject, m.Name()) cclog.Debugf("NATS %s: unexpected measurement name '%s', expected 'job'", subject, m.Name())
} }
} }
} }