* 🔭 feat: Recover Stale Chunks Without the Error Page and Ship Client Logs to RUM
Stale chunks: a tab left open across a deploy that opens a code-split panel
requests a hashed chunk the new deploy removed. Vite's preload handler hands
the failure to the stale-asset recovery, which reloads, but the import then
resolves to `undefined` and `React.lazy` throws a TypeError into the route
error boundary, so the error page flashes before the reload. Lazy imports now
go through `lazyWithRecovery`/`importWithRecovery`, which turn that result into
a `ChunkLoadError`; the route boundary recognizes chunk failures (and any error
while a recovery reload is underway), asks the page recovery once, and renders
a localized "Updating to the latest version…" status. When the loop guard
declines, the normal error page with its reload action shows instead. The
page recovery is now idempotent within a page, so concurrent callers join the
in-flight reload rather than tripping the guard.
Client logs: with RUM in proxy mode, the client logger's warn/error calls,
error-boundary catches and stale-asset recovery events are exported as OTLP
log records through the authenticated `/api/rum/v1/logs` proxy. Records carry
allowlisted, scrubbed fields only, follow RUM session sampling, dedupe repeats
with a count, are budgeted per minute and per page, batch with backoff, flush
with keepalive on page hide, and stop after persistent failures. The proxy
now refuses non-OTLP content types and applies a per-user rate limit.
`RUM_CLIENT_LOGS=false` turns the export off.
* 🔒 fix: Keep Client Logs Opt-In and Drop Application Error Messages
- RUM_CLIENT_LOGS now defaults to off, like console capture, so enabling
RUM proxy mode never starts a new log stream on its own.
- Error messages are exported only for engine, browser and library
generated types (TypeError, SyntaxError, DOMException, AxiosError,
chunk failures); application errors keep type, status and stack only,
since their messages can echo prompt or response text. All quoted
fragments are now redacted.
- Batches are measured in encoded UTF-8 bytes of the exact request body,
and page hide drains every queued record that fits the keepalive quota.
- Queued stale-asset events are delivered as soon as the log exporter
starts, independent of the RUM SDK loading, and marked so they are
never logged twice.
* 🔒 fix: Export Only Known Generated Error Messages and Ack Queued Events
- Error messages are exported only when the whole text matches a known
engine, browser or library message shape (property access on
undefined, "x is not a function", fetch/abort/axios status, chunk and
CSS preload failures). The error class alone no longer qualifies, since
any code can throw a TypeError carrying arbitrary text.
- Queued stale-asset events are marked logged only after the collector
accepts the record carrying them, so an undelivered event replays on the
next page; in-flight events are skipped by the SDK path.
- A fractional RUM_PROXY_USER_MAX below one falls back to the default
instead of flooring to a limit of zero.
* 🔒 fix: Hold Unacknowledged Asset Events, Re-send In-Flight Logs on Hide
- The RUM SDK flush no longer drops queued stale-asset events whose client
log record is still unacknowledged: they stay queued and persisted,
flagged so their SDK action is not repeated, and leave the queue once
the collector accepts the record.
- Page hide re-sends the records of an unanswered regular request with
keepalive; each record belongs to the latest request carrying it, so a
late response to the original request neither marks nor requeues it.
- Client-log export stops when the authenticated layout unmounts.
- The proxy refuses /v1/logs while client logs, console capture and replay
are all off, so turning RUM_CLIENT_LOGS off also stops tabs that still
hold an older startup config.
* 🔒 fix: Export Only Complete Stack Frames, Never the Message Header
Stack reduction now strips the V8 `name: message` header (including every
line of a multi-line message) and keeps only lines with a complete V8,
Gecko or WebKit frame shape that ends in a URL or absolute path with a
line number. A message ending in a source-position-like suffix can no
longer pass as a frame.
* fix: centralize RUM delivery and asset recovery lifecycle
* fix: preserve RUM page lifetime and collector acknowledgements
* fix: retain page transport quotas and recover functional chunks
* fix: scope RUM client sessions to authenticated identity
---------
Co-authored-by: Lia <lia@librechat.ai>