ruvector/.cargo
ruvnet 1062f0eae7 fix(ci): set RUST_MIN_STACK=16MB workspace-wide to fix rustc stack overflow
PR #389 raised `ruvector-filter`'s `recursion_limit` to 4096 to fix an
E0275 trait-resolution overflow (serde_json's `Serializer` blanket impl
chains through every variant of the filter expression AST). With that
limit in place rustc successfully *resolves* the bound, but the deeper
resolution drives rustc's own process stack past the default 8 MB
ceiling on x86_64 Linux runners — surfacing as `signal: 11, SIGSEGV` and
the diagnostic message:

  note: rustc unexpectedly overflowed its stack! this is a bug
  help: you can increase rustc's stack size by setting RUST_MIN_STACK=16777216

This trips PR test shards that touch ruvector-filter (seen on PR #391 and
PR #393). Setting `RUST_MIN_STACK=16777216` at the workspace level via
`.cargo/[env]` applies it to every `cargo` invocation locally and in CI
without per-job env wiring, and is exactly the value the rustc help text
recommends.

No code change. The fix is one .cargo/config.toml line.

Co-Authored-By: claude-flow <ruv@ruv.net>
2026-04-26 18:06:28 -04:00
..
audit.toml chore(ci): green security audit + split test job into 6 matrix shards 2026-04-26 00:17:25 -04:00
config.toml fix(ci): set RUST_MIN_STACK=16MB workspace-wide to fix rustc stack overflow 2026-04-26 18:06:28 -04:00