Skip to content

feat: connection timeline + beta workflow fix#30

Merged
colangelo merged 3 commits into
mainfrom
dev
Feb 23, 2026
Merged

feat: connection timeline + beta workflow fix#30
colangelo merged 3 commits into
mainfrom
dev

Conversation

@colangelo
Copy link
Copy Markdown
Owner

Summary

  • feat: Track alternating UP/DOWN connectivity periods, display color-coded timeline in exit summary for diagnosing intermittent outages
  • fix: Delete local beta tag before recreating release (fixes gh release create failure when tag exists locally but not remotely)

Test plan

  • go build and go test pass (19 new test cases for fmtDuration + recordPeriod)
  • Manual test: run hp-beta against flaky target, verify timeline appears on Ctrl+C
  • Beta build succeeds after workflow fix

🤖 Generated with Claude Code

colangelo and others added 3 commits February 23, 2026 22:04
Proposal, design, specs, and tasks for tracking alternating UP/DOWN
connectivity periods and displaying a timeline in the exit summary.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Track alternating UP/DOWN periods during monitoring. On exit, display
a color-coded timeline showing start times, durations, and request
counts for each period. Helps diagnose intermittent outages by making
temporal patterns visible (e.g., "drops every ~2min after recovery").

Timeline only appears when there were failures. Truncates to first 5 +
last 5 periods if connection is very flappy (>20 transitions).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
gh release create fails when the tag exists locally but not remotely.
Delete the local tag after removing the remote one.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@colangelo colangelo merged commit 9b962e5 into main Feb 23, 2026
6 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.

1 participant