Run the formatter over the shard-naming change
Build and test / android-image (push) Canceled after 1m38s
Build and test / Android (aarch64) (push) Canceled after 0s
Build and test / Desktop (Linux) (push) Canceled after 1m34s
Build and test / Layer separation (push) Canceled after 0s
🐳 Android image / Build and push (push) Canceled after 1m38s
Traceability / Requirement traces (push) Successful in 1m2s

`cargo fmt --all -- --check` is a CI gate and 9a51cc8 landed two files past
it, so the build has been red on master since regardless of what came after.
Whitespace only — a wrapped `Ok(...)` and two `assert_eq!`s split across
lines. No logic is touched and the tests are unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-16 22:29:28 +02:00
co-authored by Claude Opus 5
parent 151dcc3c02
commit 9e47133304
2 changed files with 13 additions and 5 deletions
+5 -3
View File
@@ -633,9 +633,11 @@ fn mint_client_id(conn: &Connection) -> Result<String, ThumbError> {
ON CONFLICT(key) DO NOTHING",
[],
)?;
Ok(conn.query_row("SELECT value FROM meta WHERE key = 'client_id'", [], |r| {
r.get(0)
})?)
Ok(
conn.query_row("SELECT value FROM meta WHERE key = 'client_id'", [], |r| {
r.get(0)
})?,
)
}
const SHARD_SCHEMA: &str = r#"