Google Git
Sign in
rust / rust-lang / cargo / a748cf5a3e666bc2dcdf54f37adef8ef22196452
commita748cf5a3e666bc2dcdf54f37adef8ef22196452[log] [tgz]
authorbors <bors@rust-lang.org>Wed Jun 08 23:13:47 2022 +0000
committerbors <bors@rust-lang.org>Wed Jun 08 23:13:47 2022 +0000
tree0bb6165dd4bb6fac57490d290b4e7d3d8d577fbb
parent4751950ccc948c07047e62c20adf423d7e5f668c [diff]
parent0cfdbc04721e0ca6706051c84ffd51b7f024af78 [diff]
Auto merge of #10737 - ehuss:revert-num-cpus, r=weihanglo

[beta] Revert #10427: switch from num_cpus

This temporarily reverts #10427 (Use available_parallelism instead of num_cpus) per the discussion at https://github.com/rust-lang/rust/issues/97549. `available_parallelism` does not handle cgroups v1 on Linux unlike num_cpus. I am concerned that this potentially affects a significant percentage of users. For example, Docker just added cgroups v2 support last year. Various Linux distributions have only recently switched to it as the default. The following is what I can find on the web:

* Fedora (since 31)
* Arch Linux (since April 2021)
* openSUSE Tumbleweed (since c. 2021)
* Debian GNU/Linux (since 11)
* Ubuntu (since 21.10)
* RHEL and RHEL-like distributions (since 9)

This also appears to affect CircleCI.

The consequence is that Cargo ends up using too much parallelism and can run out of memory.

I'm not sure what to do about 1.63.  If std adds support for cgroups v1, then I don't think there is anything to do there. Otherwise I think we should revert similarly if that doesn't happen.
tree: 0bb6165dd4bb6fac57490d290b4e7d3d8d577fbb
  1. .github/
  2. benches/
  3. ci/
  4. crates/
  5. src/
  6. tests/
  7. .gitignore
  8. build.rs
  9. Cargo.toml
  10. CHANGELOG.md
  11. CONTRIBUTING.md
  12. LICENSE-APACHE
  13. LICENSE-MIT
  14. LICENSE-THIRD-PARTY
  15. publish.py
  16. README.md
  17. triagebot.toml
README.md

Cargo

Cargo downloads your Rust project’s dependencies and compiles your project.

To start using Cargo, learn more at The Cargo Book.

To start developing Cargo itself, read the Cargo Contributor Guide.

Code Status

CI

Code documentation: https://docs.rs/cargo/

Installing Cargo

Cargo is distributed by default with Rust, so if you've got rustc installed locally you probably also have cargo installed locally.

Compiling from Source

Cargo requires the following tools and packages to build:

  • git
  • curl (on Unix)
  • pkg-config (on Unix, used to figure out the libssl headers/libraries)
  • OpenSSL headers (only for Unix, this is the libssl-dev package on ubuntu)
  • cargo and rustc

First, you'll want to check out this repository

git clone https://github.com/rust-lang/cargo
cd cargo

With cargo already installed, you can simply run:

cargo build --release

Adding new subcommands to Cargo

Cargo is designed to be extensible with new subcommands without having to modify Cargo itself. See the Wiki page for more details and a list of known community-developed subcommands.

Releases

Cargo releases coincide with Rust releases. High level release notes are available as part of Rust's release notes. Detailed release notes are available in this repo at CHANGELOG.md.

Reporting issues

Found a bug? We'd love to know about it!

Please report all issues on the GitHub issue tracker.

Contributing

See the Cargo Contributor Guide for a complete introduction to contributing to Cargo.

License

Cargo is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.

Third party software

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).

In binary form, this product includes software that is licensed under the terms of the GNU General Public License, version 2, with a linking exception, which can be obtained from the upstream repository.

See LICENSE-THIRD-PARTY for details.