[Bug]: Build failure with matrix-sdk v0.16.0: recursion limit overflow when building with channel-matrix feature

[rikwade]

Affected component

channel

Severity

S2 - degraded behavior

Current behavior

Build Issue

Description: Build fails when attempting to compile zeroclaw 0.7.5 with Matrix channel support enabled.

Build Command:

podman build -f Dockerfile.debian --build-arg ZEROCLAW_CARGO_FEATURES="rag-pdf channel-matrix" -t zeroclaw075 .


### Expected behavior

Container build expected to automatically compile the channel-matrix feature and include in the container build process.

### Steps to reproduce

```bash
podman build -f Dockerfile.debian --build-arg ZEROCLAW_CARGO_FEATURES="rag-pdf channel-matrix" -t zeroclaw075 .

Impact

Container build process fails

Logs / stack traces

[...]
Compiling matrix-sdk v0.16.0
error: queries overflow the depth limit!
  |
  = help: consider increasing the recursion limit by adding a #![recursion_limit = "256"] attribute to your crate (matrix_sdk)
  = note: query depth increased by 130 when computing layout of {async fn body of client::<impl at /usr/local/cargo/registry/src/index.crates.[REDACTED_HIGH_ENTROPY_TOKEN].16.0/src/client/mod.rs:488:1: 488:12>::sync()}

error: could not compile matrix-sdk (lib) due to 1 previous error

ZeroClaw version

v0.7.5

Rust version

No response

Operating system

Debian

Regression?

Unknown

Pre-flight checks

• I reproduced this on the latest master branch or latest release.
• I redacted secrets, tokens, and personal data from all submitted content.

[rikwade]

Tried increasing #![recursion_limit] in src/main.rs from 256 to 512 and 1024 — same error persists

The issue can be fixed by downgrading the rust container image from 1.94 to 1.93.
Line 27 in Dockerfile.debian

- FROM rust:1.94-bookworm AS builder
+ FROM rust:1.93-bookworm AS builder

this compiles OK, builds OK, runs OK.

[tidux]

This is a known issue upstream with the matrix-sdk crate. Waiting on their release so we can pick it up.

[singlerider]

I downgraded the severity. This is not our bug and is easily worked around by using rustc 1.93.1.