Tempo: first build is still loading the workspace after 19 min at 41 GB RSS
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce with the given cargo rustd build commands on the Tempo checkout and watch cargo rustd status show the worker loading for >1000s. Inspect the worker log at ~/.cache/rustd/spares/0/log to see where progress stops. The issue names no source file, so the workspace-loading code in rustd must be found by reading the repo.
Written by the indexing model from the issue text.
Description
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/tempoxyz/tempo && cd tempo && git checkout 60c3923
echo 1.99.0 > rust-toolchain
cargo build --bin tempo # plain cargo: 130 s
cargo rustd build --bin tempo
Expected: the daemon loads the workspace and builds. ra-jit loads this same workspace in ~40 s.
Actual: after 18 min 50 s the build was still waiting, and I stopped it:
$ cargo rustd status
daemon: pid 95109, version 0.0.0-4530fb8-18e1a8ab3799c1bb, exits after 1800s idle
worker: pid 95110, /home/ubuntu/w-rustd-tempo/, log ~/.cache/rustd/spares/0/log
/home/ubuntu/w-rustd-tempo: loading for 1126s
$ ps -o rss,args
41270388 rustd --spare ~/.cache/rustd/spares/0/package
cargo's half finished (Finished dev profile … in 4.41s in the build log). Only the worker's load never finished, and the status line gives no sign of progress. Tempo is about 30 workspace crates on top of reth (git dependencies).
- Dominant language
- Rust
- Stars
- 248
- Forks
- 13
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DioxusLabs/rustd
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
DioxusLabs/rustd#15 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
DioxusLabs/rustd#28 ·
Maintainers usually reply within 1 day
-
Workspace fails to load: rquickjs types give layout of …: HasErrorType, and rustd never falls backOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
DioxusLabs/rustd#26 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
DioxusLabs/rustd#25 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
DioxusLabs/rustd#24 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in DioxusLabs/rustd
Similar issues
-
bug rust
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxc-project/oxc-htmlish-parser#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/nsh#2541 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100