mirror of
https://github.com/Such-Software/smirk-backend-core.git
synced 2026-10-17 15:31:38 +02:00
`tracing_subscriber::fmt::init()` reads RUST_LOG when it is called, and it was called one line before `dotenvy::dotenv()`. The systemd unit sets no EnvironmentFile on purpose, so RUST_LOG exists only in .env: the filter was built with no directive and fell back to its default, ERROR. Production has logged nothing but errors since the 2026-09-20 build. On smirk-backend, `configuration loaded` has appeared zero times since, and the 01:53 restart today produced no application output at all. It hides only in production, since a developer usually has RUST_LOG exported already. This also defeats the legacy sign-in migration's designed verification. `LegacyDirectory::connect` deliberately connects at boot rather than per request so an operator reads "enabled" or "staying disabled" once, in the log. Both are `info!`, and the failure branch is a `warn!`, so all three were being dropped exactly when we need them. The guard asserts the ordering property and locates the two calls by crate rather than by line, and carries a test proving it fails on the inverted order. Also unbreak the test targets, which have not compiled on main: `AppState` gained `legacy` and `NewSocialTip` gained `recipient_user_id` without their fixtures following. Both take the closed value, off and public.