Notifications: failure diagnostics print the setup token #1271

Closed
opened 2026-10-07 00:22:09 +00:00 by kayg · 0 comments
Owner

Steps:

  1. Run bun e2e/notifications.mjs with a failing browser assertion.
  2. Inspect the failure handler in apps/web/e2e/notifications.mjs.

Expected: test diagnostics redact setup tokens before writing server logs to stderr.

Actual: the catch block prints server.log().slice(-4000) as-is. The real failure dump included the generated first-owner setup URL and token. This was a one-time token for the isolated local server; the test had consumed it during owner setup and then shut down that server.

Evidence: /home/kayg/Developer/calternal-wt/bash-core/target/tmp/notifications-log-token-redacted.txt; unredacted diagnostic call at the end of apps/web/e2e/notifications.mjs.
Severity: minor.

Steps: 1. Run `bun e2e/notifications.mjs` with a failing browser assertion. 2. Inspect the failure handler in `apps/web/e2e/notifications.mjs`. Expected: test diagnostics redact setup tokens before writing server logs to stderr. Actual: the catch block prints `server.log().slice(-4000)` as-is. The real failure dump included the generated first-owner setup URL and token. This was a one-time token for the isolated local server; the test had consumed it during owner setup and then shut down that server. Evidence: `/home/kayg/Developer/calternal-wt/bash-core/target/tmp/notifications-log-token-redacted.txt`; unredacted diagnostic call at the end of `apps/web/e2e/notifications.mjs`. Severity: minor.
kayg closed this issue 2026-10-07 20:52:27 +00:00
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal-v0#1271
No description provided.