Skip to content

F0066 log-2

Rule: DEFMT_RTT_BUFFER_SIZE and DEFMT_LOG are set in .cargo/config.toml.

Code F0066 (stable, never reused)
Id log-2
Category log
Source spirit_level
Fix by hand

Level per tier

Tier Level Reason
small off
small-workspace off
medium off
big off
ai off
embedded warn bedrock warning: DEFMT_RTT_BUFFER_SIZE and DEFMT_LOG not set explicitly in .cargo/config.toml (init bursts lost: 773 of 1000 lines)
ui off
egui off
units-strict off
units-paranoid off

Why

.cargo/config.toml relying on defmt-rtt's default buffer size and DEFMT_LOG's default level instead of setting both explicitly.

The default buffer is small enough that a burst right at boot (every "I'm alive" log a firmware tends to emit during init) can overrun it before the host even attaches; a real measurement found 773 of 1000 init-time log lines lost to exactly this.

Example

The template's own conventions call this out, and an internal log entry (Oct 2026) has the 773/1000 measurement that motivated making both settings explicit rather than left at their defaults.

How to fix

Set DEFMT_RTT_BUFFER_SIZE large enough to absorb an init burst before the host attaches, and DEFMT_LOG to the level the firmware actually wants shipped, both explicitly.

How it is checked

cfg easy: both DEFMT_RTT_BUFFER_SIZE and DEFMT_LOG must be set as explicit env vars in .cargo/config.toml, not left unset.

Source

Ported from embedded_bedrock's firmware check catalogue, LOG-2 (book/checks.md, detail in book/checks/log.md). Found on: template conventions; internal log Oct 2026.

Configure

[lints.log-2]
level = "deny"
reason = "why this project wants it at this level"

Allow one finding in the code with // spirit-level: allow(log-2) <reason> (waivers); the code works there too, as in [lints.F0066].