Workspace fails to load: rquickjs types give layout of …: HasErrorType, and rustd never falls back

Abierto
#26 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust, ubuntu
Área
compilers

Línea de trabajo

Reproduce with the nanocode repo at commit 74ef4e9 and run cargo rustd build to see the workspace load failure on rquickjs types. The fix lies in rustd's frontend layout handling and its lack of fallback to cargo, unlike ra-jit. Inspect rustd's daemon workspace loading code and add a fallback path for unsupported HasErrorType layouts; verify with cargo rustd status.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Environment: bare-metal x86-64, 48 cores, 377 GB RAM, Ubuntu 24.04, Rust 1.99.0 with rust-src, rustd nightly release 4530fb8 from install.sh (RUSTD_VERSION=nightly).

git clone https://github.com/gakonst/nanocode && cd nanocode && git checkout 74ef4e9
echo 1.99.0 > rust-toolchain
sed -i '/^rustc-wrapper/d;/^rustc-workspace-wrapper/d' .cargo/config.toml   # drop the repo's own wrappers
# work around the forbid(unsafe_code) issue first:
sed -i -E 's/^unsafe_code *= *"forbid"/unsafe_code = "allow"/' Cargo.toml
cargo rustd build -p nanocode-cli --bin nanocode

Actual: every build fails after ~47 s, and cargo rustd status shows:

/home/ubuntu/w-rustd-nanocode: failed: the daemon could not load the workspace (exit status: 1: Error: `nanocode_code_mode_engine::native::run_worker` is not compiled by rustd: unsupported: callee `drop_in_place`: callee `drop`: callee `drop_slow`: callee `drop_in_place`: … frontend: layout of Rejection: HasErrorType)

Worker log:

6  frontend: layout of ExecutionState: HasErrorType  (e.g. nanocode_code_mode_engine::cell::send_terminal)
2  frontend: layout of Option<Persistent<Function<'static>>>: HasErrorType
1  frontend: layout of Result<String, CaughtError<'…>>
1  frontend: layout of Rejection: HasErrorType  (e.g. nanocode_code_mode_engine::native::run_worker)
13 unsupported: no rustc symbol for function  (e.g. <cell::TerminalKind as serde::Deserialize>::deserialize)

One run failed with a const-eval error instead: ConstEvalError("SIZE", … LayoutError(HasErrorType, Rejection)). The crate (crates/runtime/code-mode-engine) builds on rquickjs, which has lifetime-branded types such as Persistent<Function<'static>> and Value<'js>. rust-analyzer can't type them, and because rustd never falls back, nothing in the workspace builds. The daemon reached 27 GB RSS. ra-jit hits the same HasErrorType layouts on this crate but hands those builds to cargo.

Lenguaje dominante
Rust
Estrellas
248
Forks
13
Merge medio
7 h 52 min
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DioxusLabs/rustd

Todos los issues de DioxusLabs/rustd

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.