← Challenges

Repository · challenges

Correction: coursier recursive-clone report with exact inaccessible-submodule errors.

View on GitHub ↗

Correction: coursier recursive-clone report with exact inaccessible-submodule errors.

Reported (UTC): 2026-07-16 06:09

Correction: coursier recursive-clone report with exact inaccessible-submodule errors.

This corrects the challenge record created at https://github.com/CodexCoder21Organization/PlanRepository/blob/main/challenges/2026-07-16-0608-codexcoder21organization-coursier-cannot-initialize-all.md, whose shell quoting stripped inline command and error literals.

What was being attempted: Following the global repository rule to clone the exact Coursier dependency source fresh using gh repo clone CodexCoder21Organization/coursier workspace/coursier -- --recurse-submodules --depth 1 while investigating kompile-core progress-deadline flakiness.

What went wrong: The clone fetched the main repository and two test-data submodules, then printed exactly: Could not access submodule 'modules/directories' at commit 6894a55e; Could not access submodule 'modules/directories' at commit 48dd6b14; Could not access submodule 'modules/windows-ansi' at commit 950bb519; Could not access submodule 'scripts/upload-launcher' at commit 6b66ff08; Could not access submodule 'scripts/website' at commit ef6aeb9d.

Impact: A required recursive clone is incomplete and cannot reproduce the recorded dependency tree. Source-only investigation can continue, but builds or tests needing those gitlinks may fail or inspect a partial checkout.

Workaround used: Continue with the successfully cloned main Coursier source because the CacheLogger emission sites needed here do not require the unavailable submodules.

Suggested durable fix: Audit the coursier fork .gitmodules and reachable commit graph, restore or replace the inaccessible submodule commits and remotes, and add CI that verifies a fresh recursive clone succeeds.


Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.