[Bug] : Rest quota time and usage section

[w0l4i]

hi there

i represent this two bug's that in mode : full has been accord :
#230

you said that "Otherwise I'll bundle these into v1.6.5 alongside whatever else accumulates this week." but in version 1.7.9 mhrv-rs it hasn't been added
so i humbly request to fix those bugs

best regards

[therealaleph]

@w0l4i — fair point, I owe you an update. The two bugs from #230:

1. "Usage today (estimated)" stuck at 0 in Full mode — counter increments on the apps_script-mode relay path but not on the Full-mode tunnel_client::fire_batch path
2. PST/PDT vs UTC quota reset display — we show the countdown to UTC midnight, Apps Script actually resets at midnight Pacific Time

Both are still real, both have not landed in any v1.7.x release. I deferred them through 1.6.5 → 1.7.0-1.7.11 because each release prioritized something more time-sensitive (native udpgw, Android UI restructure, deployment auto-blacklist, Win7 i686 saga, Apps Script range probe fix, etc.). That was a mistake — small bugs that get deferred quietly are exactly the ones to ship promptly.

Adding to the v1.8.x umbrella with explicit commitment to land them. Tracking as part of the existing Android UI batch I outlined in #361 reply. The batch is now:

• block_quic toggle ([FEAT] : Quic Udp 443 Block #285, [Feat] : Disable Quic in UI #361)
• youtube_via_relay toggle (Restricted Mode یوتیوب #261)
• listen_host field (اتصال سایر دستگاه های تحت شبکه #295)
• passthrough_hosts editable list (اضافه کردن bypass #254)
• Active deployment indicator (App script Unresponsive ERROR #313 Surenabedimiran)
• Full-mode usage counter wiring (this — Full mode : issues with usage section #230)
• PT-aware quota reset countdown (this — Full mode : issues with usage section #230)

Both are isolated changes:

Counter (1): in src/tunnel_client.rs::fire_batch, mirror the increment from src/domain_fronter.rs::relay() — likely a single line bumping f.relay_calls.fetch_add(...) or whatever the counter atomic is. ~5 LOC.

PT reset (2): in the UI module that renders the countdown, swap UTC midnight calculation for America/Los_Angeles midnight. Either pull chrono-tz (~150 KB binary increase, robust DST handling) or hand-roll the PT offset (~10 LOC, gets DST boundary wrong twice a year for ~1 hour). Probably worth the chrono-tz dep for correctness — DST rollover bugs are exactly the kind of thing users hit at 2am and don't bother to file. ~30 LOC if we go the dep route.

If you'd take one or both as a PR, I'd review-and-merge same day. Otherwise both ship in v1.8.x.

Sorry for the slip — should have batched a v1.7.5-ish "small fixes" release in there. Won't let it happen again on these two specifically.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}

[w0l4i]

@w0l4i — fair point, I owe you an update. The two bugs from #230:

1. "Usage today (estimated)" stuck at 0 in Full mode — counter increments on the apps_script-mode relay path but not on the Full-mode tunnel_client::fire_batch path
2. PST/PDT vs UTC quota reset display — we show the countdown to UTC midnight, Apps Script actually resets at midnight Pacific Time

Both are still real, both have not landed in any v1.7.x release. I deferred them through 1.6.5 → 1.7.0-1.7.11 because each release prioritized something more time-sensitive (native udpgw, Android UI restructure, deployment auto-blacklist, Win7 i686 saga, Apps Script range probe fix, etc.). That was a mistake — small bugs that get deferred quietly are exactly the ones to ship promptly.

Adding to the v1.8.x umbrella with explicit commitment to land them. Tracking as part of the existing Android UI batch I outlined in #361 reply. The batch is now:

• block_quic toggle ([FEAT] : Quic Udp 443 Block #285, [Feat] : Disable Quic in UI #361)
• youtube_via_relay toggle (Restricted Mode یوتیوب #261)
• listen_host field (اتصال سایر دستگاه های تحت شبکه #295)
• passthrough_hosts editable list (اضافه کردن bypass #254)
• Active deployment indicator (App script Unresponsive ERROR #313 Surenabedimiran)
• Full-mode usage counter wiring (this — Full mode : issues with usage section #230)
• PT-aware quota reset countdown (this — Full mode : issues with usage section #230)

Both are isolated changes:

Counter (1): in src/tunnel_client.rs::fire_batch, mirror the increment from src/domain_fronter.rs::relay() — likely a single line bumping f.relay_calls.fetch_add(...) or whatever the counter atomic is. ~5 LOC.

PT reset (2): in the UI module that renders the countdown, swap UTC midnight calculation for America/Los_Angeles midnight. Either pull chrono-tz (~150 KB binary increase, robust DST handling) or hand-roll the PT offset (~10 LOC, gets DST boundary wrong twice a year for ~1 hour). Probably worth the chrono-tz dep for correctness — DST rollover bugs are exactly the kind of thing users hit at 2am and don't bother to file. ~30 LOC if we go the dep route.

If you'd take one or both as a PR, I'd review-and-merge same day. Otherwise both ship in v1.8.x.

Sorry for the slip — should have batched a v1.7.5-ish "small fixes" release in there. Won't let it happen again on these two specifically.

[reply via Anthropic Claude | reviewed by @therealaleph]

tnx a lot i will wait for the release and i will be happy to test them tnx a lot