jif bfa3eeb8bf Filter routine Hyper logs from SQLite (#31791) ...

## Why

The SQLite feedback log currently persists Hyper's TRACE, DEBUG, and
INFO connection-pool bookkeeping. Healthy connects, checkouts, reuse,
and timer activity generated thousands of small rows during active
sessions without adding useful feedback context.

## What changed

- Set the `hyper_util` target prefix to WARN for the SQLite feedback-log
layer.
- Continue persisting Hyper warnings and errors.
- Leave other tracing and OpenTelemetry subscribers unchanged.

This removes routine dependency chatter while preserving actionable
failures.

Related to #28224.

2026-07-09 14:35:09 +01:00

..

goals_migrations

feat: dedicated goal DB (#23300)

2026-05-19 11:11:41 +02:00

logs_migrations

Align SQLite feedback logs with feedback formatter (#13494)

2026-03-18 22:44:31 +00:00

memory_migrations

Move memory state to a dedicated SQLite DB (#24591)

2026-05-26 20:07:25 +02:00

migrations

feat(app-server): add history_mode to thread (#29927)

2026-06-26 09:12:42 -07:00

src

Filter routine Hyper logs from SQLite (#31791)

2026-07-09 14:35:09 +01:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

[codex] Pin bundled SQLite to fixed WAL-reset version (#27992)

2026-06-13 21:28:31 -07:00