Tracking: Ensure the integrity of toolchains, handle concurrent reads/writes #3937

Activity

1. rami3l

   added

   enhancement

   tracking

   on Jul 11, 2024
2. rami3l

   changed the title [-]Tracking: Toolchain integration[/-] [+]Tracking: Ensuring the integration of toolchains[/+] on Jul 11, 2024
3. rami3l

   changed the title [-]Tracking: Ensuring the integration of toolchains[/-] [+]Tracking: Ensure the integration of toolchains[/+] on Jul 11, 2024
4. rami3l

   pinned this issue on Jul 11, 2024
5. djc commented on Jul 11, 2024

   

   djc

   on Jul 11, 2024 · Hidden as resolved

   show commentMore actions
6. rami3l

   changed the title [-]Tracking: Ensure the integration of toolchains[/-] [+]Tracking: Ensure the integrity of toolchains[/+] on Jul 11, 2024
7. rami3l

   changed the title [-]Tracking: Ensure the integrity of toolchains[/-] [+]Tracking: Ensure the integrity of toolchains, prevent concurrent read/writes[/+] on Jul 11, 2024
8. rami3l commented on Jul 11, 2024

   

   rami3l

   on Jul 11, 2024 · Hidden as resolved

   Last edited by rami3l

   Author

   show commentMore actions
9. rami3l

   changed the title [-]Tracking: Ensure the integrity of toolchains, prevent concurrent read/writes[/-] [+]Tracking: Ensure the integrity of toolchains, handle concurrent reads/writes[/+] on Jul 11, 2024
10. rami3l

    modified the milestones: 1.29.0, On Deck on Jul 16, 2024
11. rami3l

    added sub-issues on Mar 3, 2025

    • Rustup (including proxies) is not safe for concurrent use #988
    • Tracking: Rustup should not perform implicit installations #3635
    • Proposal: rustup toolchain verify #3940
    • Corrupt /missing manifests lead to installation conflicts #2417
    • running cargo in a custom toolchain is racy #2247
    • Deal with windows file locking rustup.exe + any proxies when they are executed #2441
    • rustup self uninstall failed, left system in mystery state #3330
    • Cargo is not applicable when using a toolchain specified in rust-toolchain.toml #3104
12. djc

    unpinned this issue on Mar 4, 2025
13. rami3l

    added the

    Tracking Issue

    issue type on May 7, 2025
14. rami3l

    removed

    tracking

    on May 7, 2025
15. rami3l

    added a sub-issue on Jan 27, 2026

    • Interrupted transaction could get rustup stuck in loop #4400
16. rami3l

    removed a sub-issue on Aug 16, 2026

    • Corrupt /missing manifests lead to installation conflicts #2417
17. rami3l

    added a sub-issue on Aug 21, 2026

    • Self update could interfere with itself #1864