From b618bf863d3f0ac3efc5d14bd74d1481b77e4f38 Mon Sep 17 00:00:00 2001 From: John Coffey Date: Wed, 18 Nov 2026 11:00:02 -0700 Subject: [PATCH] Build with every store backend again: box --upgrade-store's future With the release image's features (sqlite postgres mysql rocks s3 redis azure nats), main stopped compiling after #448: "queries overflow the depth limit" computing the layout of main's async block. The --upgrade-store call awaited the whole migration chain inline in main. Boxed, it no longer adds to main's layout. CI builds the default features (rocks), so it passed; the next release image build would have failed. --- crates/main/src/main.rs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/crates/main/src/main.rs b/crates/main/src/main.rs index c20a3073..8a605ac5 100644 --- a/crates/main/src/main.rs +++ b/crates/main/src/main.rs @@ -62,7 +62,10 @@ async fn main() -> std::io::Result<()> { // inbuxa: K-S3: --upgrade-store upgrades the store's layout and exits if init.upgrade_store { - std::process::exit(upgrade_store_and_exit(&init.inner.build_server()).await); + // Boxed: inline, its future made main's too deep to lay out once + // every store backend is compiled in (the release image's features) + let server = init.inner.build_server(); + std::process::exit(Box::pin(upgrade_store_and_exit(&server)).await); } // Migrate database -- 2.54.0