You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status (0.0.98): mcpp-side diagnostics landed — the opaque fetch failed (exit 1) is now an actionable message (target, configured index-repo list, the ≥2-repo gap hint, retained child output, MCPP_VERBOSE=1). The root cause is NOT in mcpp — the multi-repo resolution fix must land in xlings, tracked in openxlings/xlings#374. Keeping this open until xlings#374 is resolved (per the no-workaround discipline — mcpp diagnostics ≠ a fix).
The root cause was in xlings (openxlings/xlings#374), now fixed upstream (fix(xim): surface multi-repo install failures + best-effort catalog, commit cf9b60d5, shipped in xlings 0.4.67). mcpp 0.0.99 vendors/bundles xlings 0.4.67 (release + cross-build + e2e workflow pins bumped 0.4.62 → 0.4.67), and 0.0.98's mcpp-side diagnostics remain.
Live A/B (≥2 index_repos, same environment):
xlings 0.4.62: {"exitCode":1,"kind":"result"} — silent exit 1, zero diagnostics (the bug).
xlings 0.4.67: structured error event — {"code":"E_NOT_FOUND","hint":"searched repos: [...]","kind":"error","message":"..."} — multi-repo failures are now surfaced, exactly as this issue requested.
The xim-pkgindex install-tests (linux/macos/windows) for the 0.0.99 bump ran real multi-repo installs and passed. Closing.
Activity
chore(release): unify #230-#243 batch into a single 0.0.98 release
docs(governance): #230-#243 batch ledger + no-workaround policy + res…
fix(fetch): surface actionable diagnostics when xlings install_packag…
chore(release): bump mcpp 0.0.98 -> 0.0.99 (#237 #241 #242 #238-diag)…
docs(#238): reference filed xlings root-cause issue openxlings/xlings…
chore(release): unify #230-#243 batch into a single 0.0.98 release
Sunrisepeak commentedon Jul 18, 2026
Status (0.0.98): mcpp-side diagnostics landed — the opaque
fetch failed (exit 1)is now an actionable message (target, configured index-repo list, the ≥2-repo gap hint, retained child output,MCPP_VERBOSE=1). The root cause is NOT in mcpp — the multi-repo resolution fix must land in xlings, tracked in openxlings/xlings#374. Keeping this open until xlings#374 is resolved (per the no-workaround discipline — mcpp diagnostics ≠ a fix).docs(design): 0.0.99 batch — #243 forwarding + #238 xlings bump + #230 …
chore(deps): vendor xlings 0.4.67 for the multi-index_repo install fix (
chore(release): mcpp 0.0.98 -> 0.0.99 (#243 #238 #230)
Sunrisepeak commentedon Jul 19, 2026
Resolved in mcpp 0.0.99 (released + indexed).
The root cause was in xlings (openxlings/xlings#374), now fixed upstream (
fix(xim): surface multi-repo install failures + best-effort catalog, commit cf9b60d5, shipped in xlings 0.4.67). mcpp 0.0.99 vendors/bundles xlings 0.4.67 (release + cross-build + e2e workflow pins bumped 0.4.62 → 0.4.67), and 0.0.98's mcpp-side diagnostics remain.Live A/B (≥2 index_repos, same environment):
{"exitCode":1,"kind":"result"}— silent exit 1, zero diagnostics (the bug).errorevent —{"code":"E_NOT_FOUND","hint":"searched repos: [...]","kind":"error","message":"..."}— multi-repo failures are now surfaced, exactly as this issue requested.The xim-pkgindex install-tests (linux/macos/windows) for the 0.0.99 bump ran real multi-repo installs and passed. Closing.