Skip to content

fix: quiet federated media status probes - #5376

Merged
atomantic merged 2 commits into
mainfrom
cos/task-mtdzm58p/agent-446db876
Aug 29, 2026
Merged

fix: quiet federated media status probes#5376
atomantic merged 2 commits into
mainfrom
cos/task-mtdzm58p/agent-446db876

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Summary

  • Treat periodic federated media status discovery failures as quiet control-plane responses.
  • Authenticate and resolve peers before disclosing provider state, while naming the peer locally when real work is rejected.
  • Separate local diagnostics from federation response text and add regression coverage.

Test plan

  • cd server && npm test -- --run lib/errorHandler.test.js services/federatedMediaProvider.test.js services/federatedMediaConsumer.test.js services/instances.test.js routes/federatedMedia.test.js ../scripts/generate-api-route-catalog.test.js
  • cd server && npm test -- --exclude ../scripts/checkNpmVersion.test.js --silent=passed-only --reporter=default (35,418 passed; the omitted environment guard requires the repository npm 12 toolchain while this host currently provides npm 11)

@atomantic
atomantic merged commit 40bba55 into main Aug 29, 2026
7 checks passed
@atomantic
atomantic deleted the cos/task-mtdzm58p/agent-446db876 branch August 29, 2026 06:43
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.

1 participant