cctally 1.27.0 → 1.27.1

package/CHANGELOG.md

@@ -5,6 +5,14 @@ based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.27.1] - 2026-06-04
+
+### Fixed
+- **Three Linux-only bugs, surfaced by running the full test suite on Linux for the first time** (cctally is developed on macOS, whose case-insensitive filesystem and BSD tooling had masked them): (1) `cctally statusline` with `display.tz = utc` no longer prints a spurious `invalid timezone 'utc'; using 'UTC'` warning on Linux — the lowercase `utc` preference is now normalized to the portable IANA key `UTC` before resolution (Linux's case-sensitive zoneinfo rejects `"utc"` where macOS silently accepts it); (2) the local web dashboard's background update-check thread no longer crashes with `TypeError: 'Event' object is not callable` when the dashboard shuts down — its internal stop-event field was shadowing `threading.Thread._stop`, which `Thread.join()` invokes during teardown; (3) `cctally setup --uninstall` now reliably terminates a running legacy usage-poller on Linux even when it was launched from a long filesystem path — the process-identity check passes `ps -ww` (unlimited-width output) so Linux's default ~80-column truncation can't drop the identifying token and mis-read the live daemon as a dead PID. No action needed on upgrade.
+
+### Changed
+- **Internal (no user-facing change): the full test suite (`bin/cctally-test-all`) is now Linux-portable, and a GitHub-hosted Linux matrix (Ubuntu × Python 3.11/3.12/3.13) runs it on every tag, weekly, and on demand** — closing the cross-version verification gap left when the floor was lowered to 3.11 in 1.27.0. The portability work fixed interpreter- and OS-divergences that only ever ran on macOS before: a `pytest-xdist` timezone leak (one test pinned a Pacific `tzset()` whose libc state outlived `monkeypatch`, flipping later tests' date boundaries — now reset suite-wide via an autouse `conftest` fixture), terminal-width-dependent block-gap rendering under `COLUMNS=80`, Python 3.13's `~~~^^^` traceback caret-anchors in a migration golden, the macOS-`osascript`-vs-Linux-`notify-send` notifier-dispatch assumptions, a BSD-vs-util-linux `script` PTY invocation in the update-banner harness (now a portable `pty.spawn`), a host-config leak in the dashboard-envelope golden, and a detached background update-check that raced fixture teardown. (#132)
+
 ## [1.27.0] - 2026-06-04
 
 ### Changed

package/bin/_cctally_setup.py

@@ -998,11 +998,15 @@ def _legacy_stop_active_poller() -> str:
     # Ownership probe: the PID file is at a predictable /tmp path that
     # outlives the daemon on uncleanly exit, and macOS PIDs cycle in a
     # narrow space — verify the live process is actually our legacy
-    # poller before signaling. ps's `-o command=` emits the full cmdline
-    # with no header on both macOS BSD ps and Linux util-linux ps.
+    # poller before signaling. `-o command=` emits the cmdline with no
+    # header on both macOS BSD ps and Linux util-linux ps; `-ww` forces
+    # UNLIMITED width so the cmdline is never truncated. Without it,
+    # Linux util-linux ps clamps the column to ~80 chars (macOS BSD ps
+    # does not), so a poller launched from a long path drops the
+    # "usage-poller.py" token off the end → a false "stale-pid".
     try:
         probe = subprocess.run(
-            ["ps", "-p", str(pid), "-o", "command="],
+            ["ps", "-ww", "-p", str(pid), "-o", "command="],
             capture_output=True, text=True, timeout=2.0,
         )
     except (OSError, subprocess.TimeoutExpired):

package/bin/_cctally_statusline.py

@@ -91,6 +91,14 @@ def _resolve_statusline_tz(cli_tz, cfg, warn_once):
             tz_name = c._local_tz_name() or "UTC"
         except Exception:
             tz_name = "UTC"
+    elif tz_name and tz_name.lower() == "utc":
+        # Canonical "utc" (the value get_display_tz_pref / normalize_display_tz_value
+        # emit) -> the portable IANA key "UTC". macOS's case-insensitive
+        # filesystem resolves ZoneInfo("utc") to UTC, but Linux's case-sensitive
+        # /usr/share/zoneinfo raises ZoneInfoNotFoundError, which would emit a
+        # spurious "invalid timezone 'utc'" warning below. Mirrors
+        # resolve_display_tz, which maps canonical "utc" -> ZoneInfo("Etc/UTC").
+        tz_name = "UTC"
     try:
         ZoneInfo(tz_name)
     except (ZoneInfoNotFoundError, Exception):

package/bin/_cctally_update.py

@@ -1890,13 +1890,13 @@ class _DashboardUpdateCheckThread(threading.Thread):
         snapshot_ref: "_SnapshotRef | None" = None,
     ) -> None:
         super().__init__(name="cctally-update-check")
-        self._stop = stop_event
+        self._stop_event = stop_event
         self._hub = hub
         self._ref = snapshot_ref
 
     def run(self) -> None:
         c = _cctally()
-        while not self._stop.is_set():
+        while not self._stop_event.is_set():
             try:
                 # Self-heal runs every tick (every 30 min by default),
                 # NOT gated by `_is_update_check_due`'s 24h TTL. Catches
@@ -1938,7 +1938,7 @@ class _DashboardUpdateCheckThread(threading.Thread):
                         )
                 except Exception:
                     pass
-            self._stop.wait(c.UPDATE_DASHBOARD_CHECK_POLL_S)
+            self._stop_event.wait(c.UPDATE_DASHBOARD_CHECK_POLL_S)
 
 
 def cmd_update(args) -> int:

package/bin/cctally

@@ -2720,7 +2720,19 @@ def _post_command_update_hooks(command: str | None, args) -> None:
     ``_spawn_background_update_check`` here would create ``config.json``,
     ``update-state.json``, and ``update.log`` on a fresh install where
     the existing-install gate already makes the symlink work a no-op.
-    Same rationale as doctor."""
+    Same rationale as doctor.
+
+    Test/CI seam: ``CCTALLY_DISABLE_UPDATE_CHECK`` short-circuits the whole
+    hook (mirrors ``CCTALLY_DISABLE_DEV_AUTODETECT``). The background
+    ``_spawn_background_update_check`` is a DETACHED process that
+    ``mkdir``s APP_DIR to write ``update-state.json`` / ``update.log``; a
+    fixture harness that runs a command and then asserts on APP_DIR (e.g.
+    ``cctally-setup-test``'s uninstall-purge "data dir is gone" check)
+    otherwise races that detached writer re-creating the dir after the
+    command returns. Setting this env var makes such harnesses
+    deterministic without disabling the feature for real users."""
+    if os.environ.get("CCTALLY_DISABLE_UPDATE_CHECK"):
+        return
     if command == "setup" and getattr(args, "uninstall", False):
         return
     if command == "doctor":

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cctally",
-  "version": "1.27.0",
+  "version": "1.27.1",
   "description": "Claude Code usage tracker and local dashboard for Pro/Max subscription limits - weekly cost-per-percent trend, quota forecasts, threshold alerts. ccusage-compatible.",
   "homepage": "https://github.com/omrikais/cctally",
   "repository": {