Skip to content

v2.4.1 — fix false limit-reset alert

Choose a tag to compare

View all tags
@weltern weltern released this 11 Jul 03:39
· 127 commits to main since this release
v2.4.1
b63b498
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Bug-fix release. No user-facing features.

Fix

  • False "limit reset" + repeat "approaching limit" alert (#17) — a usage-probe response that failed (401 expired token, 429 once a window is fully capped) was being read as a genuine 0% usage sample instead of a failed probe, firing a false reset alert followed by a false re-approach alert once real data resumed. The probe now checks the HTTP response status before parsing it.
  • Confirmed against 22.5 days of local usage history: the false-zero state accounted for ~124.5h (weekly) / ~103.8h (session) of incorrect readings that didn't align with any real reset.

Tests

213 pass, including a new regression test for the fixed code path.

Verification

sha256 (also in Clawdmeter.exe.sha256):

8a93938e3a15934d89a2088b6bd59941c6b7f7f9b0097021e57d2db168107313  Clawdmeter.exe
Assets 4
Loading