No description
  • Rust 86%
  • HTML 7.8%
  • Roff 5.8%
  • Shell 0.3%
Find a file
bors ed858daaf7 Auto merge of #6771 - sgrif:sg-always-show-errors-nicely, r=alexcrichton
Always nicely show errors from crates.io if possible

Currently if Cargo ever gets a non-200 response, it will either not show
the error at all (if it was a 403 or 404), or spit out the entire
response body. Historically crates.io has served a 200 for most errors
to work around this, but we've stopped doing this as it causes problems
for other clients.

Additionally, we're starting to server more errors that have semantic
meaning (429 for rate limiting, 503 when we're in read only mode). If
the request specifies "Accept: application/json", we should ideally
return the errors formatted nicely. This isn't always true, but it's
what we'd like to do going forward.

While the output that Cargo puts out at least contains the actual
message, it's buried under a ton of useless info. This changes the
behavior so that if the response was valid JSON in the format that Cargo
expects, it just shows that (along with a description of the response
status), and only falls back to spitting out everything if it can't
parse the response body.

I'd love to add some more tests for this, but I've had trouble finding
anywhere in the test suite that exercises these paths.
2019-03-21 19:00:57 +00:00
.github/ISSUE_TEMPLATE Auto merge of #6463 - dwijnand:rip-stale-bot, r=alexcrichton 2018-12-19 14:45:14 +00:00
src Always nicely show errors from crates.io if possible 2019-03-21 12:10:43 -06:00
tests/testsuite Testsuite: Make cwd() relative to project root. 2019-03-20 16:34:56 -07:00
.gitignore Delete Cargo.lock from this repo 2017-10-18 07:43:15 -07:00
.travis.yml RIP, minimal-versions testing. You will be missed. 2019-03-16 16:55:37 -04:00
appveyor.yml Remove minimal versions build from Windows 2019-03-15 08:44:11 -07:00
ARCHITECTURE.md Fix links to point the latest docs 2019-02-24 12:21:08 +09:00
Cargo.toml Update toml requirement from 0.4.2 to 0.5.0 2019-03-18 05:35:49 +00:00
CONTRIBUTING.md Update how to install rustfmt 2019-02-23 19:30:05 +09:00
LICENSE-APACHE HTTPS all the things 2019-01-30 15:34:37 -05:00
LICENSE-MIT Remove inaccurate (misattributed) copyright notices 2017-07-26 17:19:24 -07:00
LICENSE-THIRD-PARTY HTTPS all the things 2019-01-30 15:34:37 -05:00
README.md HTTPS all the things 2019-01-30 15:34:37 -05:00

Cargo

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

Learn more at https://doc.rust-lang.org/cargo/

Code Status

Build Status Build Status

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
  • python
  • curl (on Unix)
  • 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

High level release notes are available as part of Rust's release notes. Cargo releases coincide with Rust releases.

Reporting issues

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

Please report all issues on the GitHub issue tracker.

Contributing

See CONTRIBUTING.md. You may also find the architecture documentation useful (ARCHITECTURE.md).

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.