Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

codex-cli 0.3.4 published WASM uses outdated socket ABI constants

Aperta
  • Qualcosa non va?
#1,994 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
66/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust, wasm
Ambito
build-system, networking, release, testing-qa

Direzione di ricerca

Start with toolchain/crates/libs/wasi-http/src/lib.rs and the codex-exec build and release path, then compare the published artifact with the repository constants and the host_net ABI. Use the ACP adapter at software/codex/src/adapter.ts to reproduce a session-level connection, and verify that a rebuilt published artifact passes an artifact-level network smoke test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

@agentos-software/[email protected] fails to connect to ChatGPT when used with @rivet-dev/[email protected] / @rivet-dev/[email protected]. The published codex-exec WASM artifact passes Linux socket constants to the current host_net WASI ABI.

Environment
  • macOS arm64, Node 25.8.1
  • AgentOS / core 0.2.20, Codex CLI package 0.3.4
  • Actor server/client session flow; also reproduced in a separate core VM session
  • Valid ChatGPT device-login credentials, no API key
  • ACP adapter from repository revision 0f2c8319f802dd31d43645eed88198522b8dc82a (software/codex/src/adapter.ts), because the separately published CLI artifact does not register an agent
Reproduction
  1. Install the versions above and the repository's Codex ACP adapter.
  2. Make the package executable and its directories traversable by the guest user. Supply a dedicated, guest-readable Codex home containing valid ChatGPT login credentials.
  3. Set forced_login_method = "chatgpt" and cli_auth_credentials_store = "file" in that home's config.
  4. Open a Codex session and send a simple prompt.

Session creation succeeds, but the prompt fails:

stream disconnected before completion: socket error: connect(chatgpt.com:443) failed: errno 23

The runtime's errno 23 is EHOSTUNREACH. Host HTTPS, guest JavaScript HTTPS, and guest IPv4 DNS/TCP tests succeed. A fresh actor reproduces the same error.

Artifact evidence

SHA-256 of the extracted, unmodified bin/codex-exec:

fd3c6ce268e7c952dedc1aa7df637bc26d1a2b2c7a9180130bed8cf99d86b993

Disassembly immediately before call 9 <host_net.net_socket>:

10e29c: i32.const 2
10e29e: i32.const 1
10e2a0: i32.const 0
10e2a2: local.get 2
10e2a4: i32.const 48
10e2a6: i32.add
10e2a7: call 9 <host_net.net_socket>

Current repository toolchain/crates/libs/wasi-http/src/lib.rs uses AF_INET=1 and SOCK_STREAM=6. The runner's HOST_NET_AF_INET=1, HOST_NET_AF_INET6=2, and HOST_NET_SOCK_STREAM=6 agree. The published artifact still passes 2,1.

Confirmation

For diagnosis only, I verified the hash and instruction bytes, then changed the two constants to 1,6 without changing credentials, endpoint, runtime, or adapter. Two actor server/client prompts returned the requested response using the ChatGPT subscription. This is not proposed as a shipping binary patch.

Could you rebuild/publish the Codex CLI artifact from the corrected source and add an artifact-level network smoke test? It looks like the source correction exists but has not reached this published binary. I can provide a PR if the release/build path needs a change.

Lingua principale
Rust
Stelle
4.7k
Fork
263
Merge medio
8h 57m
PR unite (30g)
30

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rivet-dev/agentos

Tutte le issue di rivet-dev/agentos

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.