(note: this is an AI generated draft/summary of some bug that happens when the KMS upgrades cosmian logger version)
Context:
Our workspace builds a wasm target (wasm32-unknown-unknown). After lockfile refresh, tracing-appender upgraded 0.2.4 -> 0.2.5 and wasm build started failing.
Repro:
Use a project that pulls tracing-appender 0.2.5 and run:
cargo build --target wasm32-unknown-unknown
Error:
E0425: cannot find function remove_symlink_file in crate symlink
E0425: cannot find function symlink_file in crate symlink
Why it happens:
tracing-appender 0.2.5 now calls symlink functions that are cfg-gated to redox/unix/windows, so they are unavailable for wasm32-unknown-unknown.
Expected:
Either:
tracing-appender should compile on wasm targets (with no-op or cfg-gated link logic), or
crate should be cfg-gated so unsupported code paths are not compiled for wasm.
Current workaround:
Pin tracing-appender to 0.2.4.
Optional secondary issue (cosmian_logger):
Ask them to avoid pulling tracing-appender on wasm targets (or gate that dependency path), since logger file-appender behavior is not meaningful on wasm.
(note: this is an AI generated draft/summary of some bug that happens when the KMS upgrades cosmian logger version)
Context:
Our workspace builds a wasm target (wasm32-unknown-unknown). After lockfile refresh, tracing-appender upgraded 0.2.4 -> 0.2.5 and wasm build started failing.
Repro:
Use a project that pulls tracing-appender 0.2.5 and run:
cargo build --target wasm32-unknown-unknown
Error:
E0425: cannot find function remove_symlink_file in crate symlink
E0425: cannot find function symlink_file in crate symlink
Why it happens:
tracing-appender 0.2.5 now calls symlink functions that are cfg-gated to redox/unix/windows, so they are unavailable for wasm32-unknown-unknown.
Expected:
Either:
tracing-appender should compile on wasm targets (with no-op or cfg-gated link logic), or
crate should be cfg-gated so unsupported code paths are not compiled for wasm.
Current workaround:
Pin tracing-appender to 0.2.4.
Optional secondary issue (cosmian_logger):
Ask them to avoid pulling tracing-appender on wasm targets (or gate that dependency path), since logger file-appender behavior is not meaningful on wasm.