Skip to content

Show driver cache sizes in bytes - #182

Merged
jcombs-pointblue merged 1 commit into
mainfrom
cache-size-bytes
Nov 2, 2026
Merged

jcombs-pointblue merged 1 commit into
mainfrom
cache-size-bytes

Conversation

@jcombs-pointblue

Copy link
Copy Markdown
Contributor

The engine reports a driver's cache as its size in bytes (GetDriverStats), but the page showed a bare number. On edir3 the AD driver showed 465, which reads as 465 queued events; it was 2. The same fix went into core in DirXMLDev#121 for engine.stats and driver.status.

What changes

  • cacheBytes() in web/src/drivers.ts: a number gets bytes; anything else (?, empty) is left as it is.
  • Where it's used:
    • Vault → Drivers: the Cache column;
    • the engine counters table: Cache and Unprocessed;
    • a driver's status: Cache … · unprocessed …;
    • the Architecture view's driver tooltip.
  • JSON unchanged: the fields cacheSize and unprocessedSize keep their names and values.

Checked

  • drivers.test.ts: new; vitest runs 56 tests across 14 files, all passing.
  • npm run build (type check) passes.
  • Live: a local server on the edir3 tree, Vault → Drivers on edir3, showed 0 bytes, 4843 bytes, 1990 bytes and so on. view still counts the events (FS2: 4843 bytes, 22 events).

🤖 Generated with Claude Code

The engine reports a driver's cache as its size in bytes. The Drivers tab,
engine counters, driver status and the Architecture tooltip showed the
bare number, which reads as a count of events (465 bytes was 2 events).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jcombs-pointblue
jcombs-pointblue merged commit 4d49385 into main Nov 2, 2026
2 checks passed
@jcombs-pointblue
jcombs-pointblue deleted the cache-size-bytes branch November 2, 2026 22:30
jcombs-pointblue added a commit that referenced this pull request Nov 3, 2026
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