Main doesn't compile with the release image's features since #448 (mine):
cargo build --release -p inbuxa --no-default-features --features "sqlite postgres mysql rocks s3 redis azure nats"
error: queries overflow the depth limit!
= note: query depth increased by 130 when computing layout of `{async block@crates/main/src/main.rs:50:1: 50:15}`
--upgrade-store awaited the whole migration chain inline in main. Boxing that future keeps it out of main's layout. One line, plus a comment saying why.
Why CI was green:ci.yml builds -p inbuxa with the default features (rocks only), debug and release. Only the publish build (the Dockerfile) uses every backend, so the next release image would have failed. Found while building a lab image from main for the chart.
Tested
The release-features build above: finishes (17 m 36 s).
That binary: --upgrade-store on a new RocksDB store → The store layout is at version 3: nothing to upgrade., exit 0.
fmt ok.
Worth considering (not in this PR): a CI step that builds with the release features, so a break like this shows on the PR. A cargo check would be cheaper and catches feature-gated code, but I haven't confirmed it catches a layout error like this one. Either costs CI time on the shared runner, so it's your call.
Main doesn't compile with the release image's features since #448 (mine):
```
cargo build --release -p inbuxa --no-default-features --features "sqlite postgres mysql rocks s3 redis azure nats"
error: queries overflow the depth limit!
= note: query depth increased by 130 when computing layout of `{async block@crates/main/src/main.rs:50:1: 50:15}`
```
`--upgrade-store` awaited the whole migration chain inline in `main`. Boxing that future keeps it out of `main`'s layout. One line, plus a comment saying why.
**Why CI was green:** `ci.yml` builds `-p inbuxa` with the default features (`rocks` only), debug and release. Only the publish build (the Dockerfile) uses every backend, so the next release image would have failed. Found while building a lab image from main for the chart.
**Tested**
- The release-features build above: finishes (17 m 36 s).
- That binary: `--upgrade-store` on a new RocksDB store → `The store layout is at version 3: nothing to upgrade.`, exit 0.
- fmt ok.
**Worth considering (not in this PR):** a CI step that builds with the release features, so a break like this shows on the PR. A `cargo check` would be cheaper and catches feature-gated code, but I haven't confirmed it catches a layout error like this one. Either costs CI time on the shared runner, so it's your call.
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 18:00:11 +00:00
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Main doesn't compile with the release image's features since #448 (mine):
--upgrade-storeawaited the whole migration chain inline inmain. Boxing that future keeps it out ofmain's layout. One line, plus a comment saying why.Why CI was green:
ci.ymlbuilds-p inbuxawith the default features (rocksonly), debug and release. Only the publish build (the Dockerfile) uses every backend, so the next release image would have failed. Found while building a lab image from main for the chart.Tested
--upgrade-storeon a new RocksDB store →The store layout is at version 3: nothing to upgrade., exit 0.Worth considering (not in this PR): a CI step that builds with the release features, so a break like this shows on the PR. A
cargo checkwould be cheaper and catches feature-gated code, but I haven't confirmed it catches a layout error like this one. Either costs CI time on the shared runner, so it's your call.