Repository navigation
feat(lfs): record handler outcomes and honest byte metrics - #57
Conversation
yordis
commented
Oct 31, 2026
- LFS handlers had no outcome metrics, so failures and rejected uploads were invisible to operators.
- Byte counters must distinguish what a client offered from what was validated and stored, or dashboards overstate real traffic.
- Brings in feat(lfs): record handler outcomes and honest byte metrics tobi/walgit#62 by Tobi Lütke, cherry-picked with original authorship.
PR SummaryLow Risk Overview GET responses additionally feed
Reviewed by Cursor Bugbot for commit 1c9c775. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Adapt PR #51 with explicit offered-download and validated-upload counters. Exclude HEAD/304/error/offloaded responses; count HTTP errors even when returned as Ok(Response). A recorder regression covers range and dropped-response semantics. (cherry picked from commit e21a078) Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
6d26fde to
1c9c775
Compare