Bug: mohu-compute and mohu-linalg listed as git deps pointing to non-existent repos

[Bbn08]

The workspace Cargo.toml lists two external git dependencies that do not yet exist:

mohu-compute = { git = "https://github.com/mohu-org/mohu-compute" }
mohu-linalg  = { git = "https://github.com/mohu-org/mohu-linalg" }

Any cargo build --workspace or cargo check run will attempt to fetch these repos and fail with a git error when network access is available, or resolve to a stale lockfile entry in CI.

These entries should be removed from the workspace dependency table until the respective repositories exist. Crates that will eventually depend on them should use feature flags or optional dependencies in the interim.

Signed-off-by: mohu-org atrancendentbeing@gmail.com

[agamsharma172008]

Hi, I’m interested in working on this issue under GSSoC. Before starting, I wanted to confirm whether this issue is considered eligible for GSSoC contributions.

[Mahesh-forcode]

Hi @Bbn08

I'd like to work on this issue as part of GSSoC '26. Could you please assign it to me?

My understanding of the problem:

The workspace Cargo.toml declares two external git dependencies that point to repos that don't yet exist:

# ── External mohu-org crates (separate repos) ─────────────────────────────────
mohu-compute = { git = "https://github.com/mohu-org/mohu-compute" }
mohu-linalg  = { git = "https://github.com/mohu-org/mohu-linalg" }

This causes cargo build --workspace and cargo check to fail with a git fetch error whenever network access is available, and risks stale lockfile entries in CI.

Proposed fix:

1. Remove both entries from [workspace.dependencies] in the root Cargo.toml.
2. Audit each internal crate that references mohu-compute or mohu-linalg and gate those dependencies behind an optional feature flag (e.g. compute / linalg) so the workspace still compiles cleanly without them.
3. Add a note in CRATE_MAP.md or ROADMAP.md marking these crates as "planned — not yet published" so future contributors know they're stubs.

I've already reviewed the codebase and am confident I can land a clean, well-tested PR for this. Happy to discuss the approach before diving in.

Thanks!

[github-actions]

Assigned to @Pcmhacker-piro ✓

[github-actions]

Assigned to @Pcmhacker-piro ✓

[sudha09-git]

/assign

[github-actions]

This issue is already assigned to @Pcmhacker-piro.