FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

docs: make retry demo failure count obvious by lesnik512 · Pull Request #110 · modern-python/httpware · GitHub

docs: make retry demo failure count obvious - #110

Merged
lesnik512 merged 1 commit into
mainfrom
retry-demo-failures-visibility
Jul 19, 2026
Merged

docs: make retry demo failure count obvious#110
lesnik512 merged 1 commit into
mainfrom
retry-demo-failures-visibility

Conversation

Copy link
Copy Markdown
Member

Follow-up to #109. On the live retry demo the failure count — the whole payoff of the page — wasn't obvious: it used the muted label style, the blip stops spotlighted the in-flight counters (while the copy said "compare the ✗ counts"), and the 1.2s blip let httpware recover only ~5 of ~14 failures.

Spec: planning/changes/2026-07-19.01-retry-demo-failures-visibility.md.

Changes

  • ✗ failed is now a prominent stat (bold number, red when > 0), wrapped in a spotlightable element, on all demo pages.
  • Retry blip stops spotlight the ✗ counts (plain climbing vs httpware staying ~0) instead of in-flight.
  • Tightened the blip to 0.4s so httpware recovers all of it — plain ✗6, httpware ✗0 (was ✗14 vs ✗9). The sustained scenario is unchanged: retry can't reduce failures in a real outage (that's the "don't amplify" point, not "fewer failures").

Verification

  • just docs-build --strict clean; just check-planning OK.
  • Headless jsdom harnesses green (real-order load + every scenario's tour); trace confirms the blip contrast (plain ✗6 / httpware ✗0) and the sustained budgetExhausted stop still fires.

🤖 Generated with Claude Code

The retry page's whole point is that httpware surfaces fewer failures to the
caller, but the failed count was rendered in the muted label style, the blip
stops spotlighted the in-flight counters (while the copy said 'compare the ✗
counts'), and the 1.2s blip left httpware recovering only ~5 of ~14 — a weak
contrast.

- ✗ failed is now a prominent stat (bold number, red when >0), wrapped in a
  spotlightable element, on all pages
- retry blip stops spotlight the ✗ counts (plain climbing vs httpware ~0)
- tighten the blip to 0.4s so httpware recovers all of it: plain ✗6, httpware ✗0

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lesnik512 merged commit 2168d98 into main Jul 19, 2026
7 checks passed
lesnik512 deleted the retry-demo-failures-visibility branch July 19, 2026 13:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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


Back | FazBrowse Home | New Git URL