Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

master CI red since 3d16d77db: jcode-app-core lib tests do not compile on Windows (E0433, tests module gated not(windows))

Open Beginner friendly
  • Is something wrong?
#2,019 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
ci-cd, testing

Research direction

Start with the cfg gates and call site in crates/jcode-app-core/src/tool/bash.rs around lines 1310 and 1491, then inspect bash_tests.rs to see which test pieces are platform-specific. Reproduce with the Windows target command given in the issue. Done means the library test target compiles on Windows and the test launch gate is consistently gated.

Written by the indexing model from the issue text.

Description

Summary

Since 3d16d77db (2026-10-30), the Build & Test (windows-latest) CI job cannot compile the jcode-app-core library test target on master: error[E0433]: cannot find module or crate tests`` at crates/jcode-app-core/src/tool/bash.rs:1310. The commit is `bce1bbecb` (per-session environment snapshot, #1969).

Steps to reproduce
  1. Check out master at 3d16d77db or newer on Windows, or read any CI run since https://github.com/1jehuang/jcode/actions/runs/41042420189 (job Build & Test (windows-latest)).
  2. Build the test target: cargo test --locked --target x86_64-pc-windows-msvc --lib --bins --no-run.
Expected

The library test target compiles on Windows.

Actual

error[E0433]: cannot find module or crate tests in this scope pointing at bash.rs:1310:

  • The call site is gated #[cfg(test)] only: tests::wait_for_session_env_launch_gate(&session_id_env).await;
  • But the module is declared #[cfg(all(test, not(windows)))] with #[path = "bash_tests.rs"] mod tests; (bash.rs:1491-1493), so on Windows tests does not exist at all.
    Every master CI run since 3d16d77db fails this step (runs 41042420189, 41018079592 and the three before it), and PR runs that compile app-core lib tests fail identically.
Proposed fix

Align the two cfg gates. Either widen the module to #[cfg(test)] and keep the unix-only pieces inside bash_tests.rs under their own #[cfg(unix)] guards, or gate the call site #[cfg(all(test, not(windows)))] to match the module. The call is a test launch gate, so matching the module gate is the smaller change.

Happy to open a PR if you want.

Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 3h
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 1jehuang/jcode

All issues in 1jehuang/jcode

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.