Skip to content

feat(app): pipeline warnings — surface non-fatal issues in menu bar#60

Merged
pasrom merged 2 commits intomainfrom
feat/pipeline-warnings
Mar 22, 2026
Merged

feat(app): pipeline warnings — surface non-fatal issues in menu bar#60
pasrom merged 2 commits intomainfrom
feat/pipeline-warnings

Conversation

@pasrom
Copy link
Copy Markdown
Owner

@pasrom pasrom commented Mar 22, 2026

Summary

Cherry-picked from execsumo/meeting-transcriber fork:

  • Add warnings: [String] array to PipelineJob for non-fatal pipeline issues
  • Jobs with warnings show warning text in orange and yellow status dot (vs. green for clean completion)
  • Warnings survive JSON encoding (snapshot persistence)

Changes

  • PipelineJob.swift: Add warnings array, initialized empty, Codable
  • MenuBarView.swift: jobColor() takes PipelineJob instead of JobState, returns .yellow when warnings present; warning text displayed in orange below job title

Test plan

  • testWarningsSurviveEncoding — warnings persist through JSON round-trip
  • testWarningJobShowsWarningText — warning text renders in menu bar
  • Full suite: 754 tests, 0 failures

execsumo and others added 2 commits March 22, 2026 11:50
Track non-fatal warnings (e.g. diarization failures, speaker naming
skipped) on the job model so they can be surfaced in notifications
when the protocol completes.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Jobs with warnings display the warning text in orange and use a yellow
status dot instead of green, distinguishing partial-success from clean
completion.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added the enhancement New feature or request label Mar 22, 2026
@pasrom pasrom merged commit 93894d9 into main Mar 22, 2026
7 checks passed
@pasrom pasrom deleted the feat/pipeline-warnings branch March 22, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants