The /code box resolved Maven publication through a wrong-architecture /usr/local/bin/coursier

Reported (UTC): 2026-07-16 08:38

The /code box resolved Maven publication through a wrong-architecture /usr/local/bin/coursier binary.

What was being attempted: Publish community.kotlin.libp2p:jvm-libp2p:1.3.0-codexcoder21-snapshot-17 to kotlin.directory with the documented publish-maven-artifact CLI after a successful Gradle publishToMavenLocal build.

What went wrong: The exact publisher command failed before contacting the upload API with exit code 126 and '/bin/bash: line 8: /usr/local/bin/coursier: cannot execute binary file: Exec format error'. A working launcher exists at /home/christian/bin/cs, but the task's strict stop-on-any-publish-failure rule prohibited retrying the artifact publication.

Impact: The jvm-libp2p snapshot-17 publish chain stopped before upload, so UrlProtocol 0.0.366 and the downstream UrlResolver stress verification could not proceed.

Workaround used: None for the blocked publication because the user explicitly required STOP on a failed publish. The working /home/christian/bin/cs launcher was used only to file this challenge.

Suggested durable fix: Replace /usr/local/bin/coursier with a native binary for this host architecture, or ensure /home/christian/bin provides a coursier alias ahead of /usr/local/bin so documented coursier commands cannot select the broken launcher.

---

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.