4 ms·
This is giving me an error: > rustup component add miri --toolchain=nightly info: downloading component 'miri' info: installing component 'miri'
by leshow 8y ago
This is giving me an error:
> rustup component add miri --toolchain=nightly
info: downloading component 'miri'
info: installing component 'miri'
info: rolling back changes
error: component manifest for 'miri' is corrupt
If Miri as in interpreter, are there any plans to bring a REPL to Rust? It's one thing I sorely miss.
- steveklabnik 8y agoAre you on the latest nightly? It will only work on the latest nightly, and going forward into the future. There’s another sub-thread on HN about that, check it out :)
- Vinnl 8y agoNamely here, in case they drift apart: https://news.ycombinator.com/item?id=19501277 https://news.ycombinator.com/item?id=19501277 :)
- nmdeadhead 8y agoFWIW, I manually attempt to update to nightly (nightly-x86_64-apple-darwin) once a day, not because I need to, but out of curiosity. I find that clippy often prevents me from updating for a day or two before working again. Today happens to be a day (and I think yesterday was, too) when I get: "error: component 'clippy' for target 'x86_64-apple-darwin' is unavailable for download for channel 'nightly'" and sure enough, I get the misleading "manifest for 'miri' is corrupt" when I try to add miri. Surprisingly, I used "rustup component remove clippy" and still couldn't update to nightly, still with a complaint about clippy. I'm not mentioning any of the above because it bothers me; I expect things to work tomorrow or the next day. I just assume this might be biting a lot of people (perhaps everyone on MacOS).
- Manishearth 8y agoYeah, the tools team is looking into providing a nightly-with-tools experience that's smoother about this stuff.
- steveklabnik 8y agoYep, that's the issue with nightly builds: you're living on the edge, and sometimes, you get cut :/ Totally, and I appreciate it. Good luck. :)