mozilla
/
sccache
зеркало из https://github.com/mozilla/sccache.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
sccache/Cargo.lock

3869 строки
93 KiB
Plaintext
Исходник Обычный вид История

involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
`cargo update`
2020-06-11 04:40:05 +03:00
[[package]]
name = "addr2line"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.14.1"
`cargo update`
2020-06-11 04:40:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "a55f82cfe485775d02112886f4169bde0c5894d75e79ead7eafe7e40a25e45f7"
`cargo update`
2020-06-11 04:40:05 +03:00
dependencies = [
"gimli",
]
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "adler"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee2a4ec343196209d6594e19543ae87a39f96d5534d7174822a3ad825dd6ed7e"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "aho-corasick"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.7.15"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "7404febffaa47dac81aa44dba71523c9d069b1bdc50a77db41195149e17f68e5"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"memchr",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "ansi_term"
Silence some warnings
2018-07-12 13:46:33 +03:00
version = "0.11.0"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Change error handling from `error-chain` to `anyhow`. Because `anyhow` is what seems to be the most common error library for applications these days. - The global `Result` type is now `anyhow::Result`. - In errors.rs, there's no need for any boilerplate to wrap all the foreign errors seen: `hyper::Error`, `io:Error`, etc. - The internal errors that we care about are now separate types, rather than within an enum, because that works better when we need to check for them by downcasting an `anyhow::Error`. And it's nice to write `Err(ProcessError(output))` rather than `Err(ErrorKind::ProcessError(output))`. - The `Which` error was unused and is removed. - The most common change is that `.chain_err()` is changed to `.context`/`.with_context()`. - `anyhow!` is used where necessary, mostly to promote a string to an `anyhow::Error`. - Errors within futures: `FutureChainErr`/`.chain_err()` is changed to `FutureContext`/`fcontext`/`fwith_context`. The `f` prefix is because I found it helpful to distinguish these cases from the simple error cases. - `BuilderIncoming`, `SchedulerIncoming`, `ServerIncoming` no longer have an `Error` associated type, we just use `anyhow::Error` uniformly. - `e.display_chain()` changes to `format!("{:?}")`, because they both print the full cause chain, and the backtrace (if present). - A few places where the old code was doing something weird or more complicated than seemed necessary, I generally tried to replace it with something simpler and more typical. Two places used `with_boxed_chain()`, which doesn't have an equivalent in `anyhow`, so I did my best to do something reasonable. - In `src/server.rs` we now import `std::task::Context` as `TaskContext` to avoid overshadowing the `anyhow::Context` trait :(
2020-06-02 10:22:31 +03:00
[[package]]
name = "anyhow"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.37"
Change error handling from `error-chain` to `anyhow`. Because `anyhow` is what seems to be the most common error library for applications these days. - The global `Result` type is now `anyhow::Result`. - In errors.rs, there's no need for any boilerplate to wrap all the foreign errors seen: `hyper::Error`, `io:Error`, etc. - The internal errors that we care about are now separate types, rather than within an enum, because that works better when we need to check for them by downcasting an `anyhow::Error`. And it's nice to write `Err(ProcessError(output))` rather than `Err(ErrorKind::ProcessError(output))`. - The `Which` error was unused and is removed. - The most common change is that `.chain_err()` is changed to `.context`/`.with_context()`. - `anyhow!` is used where necessary, mostly to promote a string to an `anyhow::Error`. - Errors within futures: `FutureChainErr`/`.chain_err()` is changed to `FutureContext`/`fcontext`/`fwith_context`. The `f` prefix is because I found it helpful to distinguish these cases from the simple error cases. - `BuilderIncoming`, `SchedulerIncoming`, `ServerIncoming` no longer have an `Error` associated type, we just use `anyhow::Error` uniformly. - `e.display_chain()` changes to `format!("{:?}")`, because they both print the full cause chain, and the backtrace (if present). - A few places where the old code was doing something weird or more complicated than seemed necessary, I generally tried to replace it with something simpler and more typical. Two places used `with_boxed_chain()`, which doesn't have an equivalent in `anyhow`, so I did my best to do something reasonable. - In `src/server.rs` we now import `std::task::Context` as `TaskContext` to avoid overshadowing the `anyhow::Context` trait :(
2020-06-02 10:22:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "ee67c11feeac938fae061b232e38e0b6d94f97a9df10e6271319325ac4c56a86"
Change error handling from `error-chain` to `anyhow`. Because `anyhow` is what seems to be the most common error library for applications these days. - The global `Result` type is now `anyhow::Result`. - In errors.rs, there's no need for any boilerplate to wrap all the foreign errors seen: `hyper::Error`, `io:Error`, etc. - The internal errors that we care about are now separate types, rather than within an enum, because that works better when we need to check for them by downcasting an `anyhow::Error`. And it's nice to write `Err(ProcessError(output))` rather than `Err(ErrorKind::ProcessError(output))`. - The `Which` error was unused and is removed. - The most common change is that `.chain_err()` is changed to `.context`/`.with_context()`. - `anyhow!` is used where necessary, mostly to promote a string to an `anyhow::Error`. - Errors within futures: `FutureChainErr`/`.chain_err()` is changed to `FutureContext`/`fcontext`/`fwith_context`. The `f` prefix is because I found it helpful to distinguish these cases from the simple error cases. - `BuilderIncoming`, `SchedulerIncoming`, `ServerIncoming` no longer have an `Error` associated type, we just use `anyhow::Error` uniformly. - `e.display_chain()` changes to `format!("{:?}")`, because they both print the full cause chain, and the backtrace (if present). - A few places where the old code was doing something weird or more complicated than seemed necessary, I generally tried to replace it with something simpler and more typical. Two places used `with_boxed_chain()`, which doesn't have an equivalent in `anyhow`, so I did my best to do something reasonable. - In `src/server.rs` we now import `std::task::Context` as `TaskContext` to avoid overshadowing the `anyhow::Context` trait :(
2020-06-02 10:22:31 +03:00
Cheat when creating rlibs by only sending metadata
2018-09-04 22:36:28 +03:00
[[package]]
name = "ar"
upgrade ar crate so we can do less copying when trimming rlibs The current trimming of rlibs in the dist-sccache case looks like: 1. Find the `rust.metadata.bin` file in the rlib (archive). 2. Read its data. 3. Create a new archive that will only contain said file. 4. Copy the data into the new archive. We can do better than this, by doing the following: 1. Find the `rust.metadata.bin` file in the rlib (archive). 2. Create a new archive that will only contain said file. 3. Copy the data from the original rlib directly into the new archive. We thus save a copy. All that being said, it looks like recent versions of Rust don't actually output `rust.metadata.bin` files into rlibs...unless we ought to be only taking the `lib.rmeta` file that lives inside the archive. But that would be a separate fix. (It's also great that we're seemingly copying the rmeta file twice, once because it lives in the rlib and once because it lives on disk as a separate file...)
2020-06-10 16:31:32 +03:00
version = "0.8.0"
Cheat when creating rlibs by only sending metadata
2018-09-04 22:36:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade ar crate so we can do less copying when trimming rlibs The current trimming of rlibs in the dist-sccache case looks like: 1. Find the `rust.metadata.bin` file in the rlib (archive). 2. Read its data. 3. Create a new archive that will only contain said file. 4. Copy the data into the new archive. We can do better than this, by doing the following: 1. Find the `rust.metadata.bin` file in the rlib (archive). 2. Create a new archive that will only contain said file. 3. Copy the data from the original rlib directly into the new archive. We thus save a copy. All that being said, it looks like recent versions of Rust don't actually output `rust.metadata.bin` files into rlibs...unless we ought to be only taking the `lib.rmeta` file that lives inside the archive. But that would be a separate fix. (It's also great that we're seemingly copying the rmeta file twice, once because it lives in the rlib and once because it lives on disk as a separate file...)
2020-06-10 16:31:32 +03:00
checksum = "450575f58f7bee32816abbff470cbc47797397c2a81e0eaced4b98436daf52e1"
Cheat when creating rlibs by only sending metadata
2018-09-04 22:36:28 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "arrayref"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.3.6"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "a4c527152e37cf757a3f78aae5a06fbeefdb07ccc535c980a3208ee3060dd544"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "arrayvec"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.2"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "23b62fc65de8e4e7f52534fb52b0f3ed04746ae267519eef2a83941e8085068b"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "ascii"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
version = "0.8.7"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "97be891acc47ca214468e09425d02cef3af2c94d0d82081cd02061f996802f14"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
[[package]]
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
name = "assert_cmd"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.0.2"
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "3dc1679af9a1ab4bea16f228b05d18f8363f8327b1fa8db00d2760cfafc6b61e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
update test harness crates This patch looks like a routine crate version update, but it fixes something very fundamentally wrong with the tests: `escargot`, to find the `sccache` binary during tests, would actually run `cargo build` and parse the output. There were all manner of hacks to try and build the binary with the correct set of features, none of which were reliable, and the hacks were not reliably present in all places, either. When the hacks were not present, `escargot` would rebuild the entire sccache crate, which was responsible for the `sccache_cargo` test taking entirely too long. When the hacks failed utterly, perfectly fine patches would mysteriously fail, as seen in #774. We can get rid of `escargot` because `assert-cmd` has been updated to a) not use `escargot` under the hood; and b) do something smarter to locate the target binary. The upshot is fewer mysterious test failures and significantly faster running tests.
2020-06-05 01:34:11 +03:00
"doc-comment",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"predicates",
"predicates-core",
"predicates-tree",
update test harness crates This patch looks like a routine crate version update, but it fixes something very fundamentally wrong with the tests: `escargot`, to find the `sccache` binary during tests, would actually run `cargo build` and parse the output. There were all manner of hacks to try and build the binary with the correct set of features, none of which were reliable, and the hacks were not reliably present in all places, either. When the hacks were not present, `escargot` would rebuild the entire sccache crate, which was responsible for the `sccache_cargo` test taking entirely too long. When the hacks failed utterly, perfectly fine patches would mysteriously fail, as seen in #774. We can get rid of `escargot` because `assert-cmd` has been updated to a) not use `escargot` under the hood; and b) do something smarter to locate the target binary. The upshot is fewer mysterious test failures and significantly faster running tests.
2020-06-05 01:34:11 +03:00
"wait-timeout",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "async-channel"
version = "1.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "59740d83946db6a5af71ae25ddf9562c2b176b2ca42cf99a455f09f4a220d6b9"
dependencies = [
"concurrent-queue",
"event-listener",
"futures-core",
]
[[package]]
name = "async-executor"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eb877970c7b440ead138f6321a3b5395d6061183af779340b65e20c0fede9146"
dependencies = [
"async-task",
"concurrent-queue",
"fastrand",
"futures-lite",
"once_cell",
"vec-arena",
]
[[package]]
name = "async-global-executor"
version = "1.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73079b49cd26b8fd5a15f68fc7707fc78698dc2a3d61430f2a7a9430230dfa04"
dependencies = [
"async-executor",
"async-io",
"futures-lite",
"num_cpus",
"once_cell",
]
[[package]]
name = "async-io"
version = "1.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9315f8f07556761c3e48fec2e6b276004acf426e6dc068b2c2251854d65ee0fd"
dependencies = [
"concurrent-queue",
"fastrand",
"futures-lite",
"libc",
"log 0.4.11",
"nb-connect",
"once_cell",
"parking",
"polling",
"vec-arena",
"waker-fn",
"winapi 0.3.9",
]
[[package]]
name = "async-mutex"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "479db852db25d9dbf6204e6cb6253698f175c15726470f78af0d918e99d6156e"
dependencies = [
"event-listener",
]
[[package]]
name = "async-std"
version = "1.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f9f84f1280a2b436a2c77c2582602732b6c2f4321d5494d6e799e6c367859a8"
dependencies = [
"async-channel",
"async-global-executor",
"async-io",
"async-mutex",
"blocking",
"crossbeam-utils 0.8.1",
"futures-channel",
"futures-core",
"futures-io",
"futures-lite",
"gloo-timers",
"kv-log-macro",
"log 0.4.11",
"memchr",
"num_cpus",
"once_cell",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"pin-project-lite 0.2.1",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"pin-utils",
"slab",
"wasm-bindgen-futures",
]
[[package]]
name = "async-task"
version = "4.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e91831deabf0d6d7ec49552e489aed63b7456a7a3c46cff62adad428110b0af0"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
[[package]]
name = "async-trait"
version = "0.1.42"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8d3a45e77e34375a7923b1e8febb049bb011f064714a8e17a1a616fef01da13d"
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
]
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "atomic-waker"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "065374052e7df7ee4047b1160cca5e1467a12351a40b3da123c870ba0b8eda2a"
Update clap
2017-04-05 17:42:06 +03:00
[[package]]
name = "atty"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.2.14"
Update clap
2017-04-05 17:42:06 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"hermit-abi",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update clap
2017-04-05 17:42:06 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "autocfg"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "1d49d90015b3c36167a20fe2810c5cd875ad504b39cff3d4eae7977e6b7c1cb2"
Update deps.
2019-12-10 00:17:20 +03:00
cargo update
2020-04-28 07:55:50 +03:00
[[package]]
name = "autocfg"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.0.1"
cargo update
2020-04-28 07:55:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
cargo update
2020-04-28 07:55:50 +03:00
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
[[package]]
name = "backtrace"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.3.55"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "ef5140344c85b01f9bbb4d4b7288a8aa4b3287ccef913a14bcc78a1063623598"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
`cargo update`
2020-06-11 04:40:05 +03:00
"addr2line",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Don't enable deflate on the zip crate It's not needed since be9da57. This allows to update the flate2 crate for reqwest.
2020-12-08 10:54:34 +03:00
"miniz_oxide",
`cargo update`
2020-06-11 04:40:05 +03:00
"object",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"rustc-demangle",
]
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
[[package]]
name = "base64"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
version = "0.9.3"
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "489d6c0ed21b11d038c31b6ceccca973e65d73ba3bd8ecb9a2babf5546164643"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"safemem",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
[[package]]
name = "base64"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
]
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "base64"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3441f0f7b02788e948e47f457ca01f1d7e6d92c693bc132c22b087d3141c03ff"
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "base64"
version = "0.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "904dfeac50f3cdaba28fc6f57fdcddb75f49ed61346676a78c4ffe55877802fd"
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
Update other deps
2018-01-07 18:58:55 +03:00
name = "bincode"
version = "0.8.0"
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "e103c8b299b28a9c6990458b7013dc4a8356a9b854c51b9883241f5866fac36e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
"num-traits 0.1.43",
"serde",
]
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "bincode"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.3.1"
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "f30d3a39baa26f9651f17b375061f3233dde33424a8b72b0dbe93a68a0bc896d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
"serde",
]
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
[[package]]
name = "bitflags"
Update deps.
2019-12-10 00:17:20 +03:00
version = "1.2.1"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "blake2b_simd"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.11"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "afa748e348ad3be8263be728124b24a24f268266f6f5d58af9d75f6a40b5c587"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"arrayref",
"arrayvec",
"constant_time_eq",
]
Switch from SHA-512 to BLAKE3 BLAKE3 is designed to be a very high performance cryptographic hash. The BLAKE3 team has shown 8.5x higher single-thread performance than SHA-512 on modern server hardware (AWS `c5.metal`). This change did not result in a significant improvement to my observed local build times, but newer hardware may see a meaningful improvement. Signed-off-by: George Hahn <george.hahn.vhs@gmail.com>
2020-01-17 09:29:27 +03:00
[[package]]
name = "blake3"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.3.7"
Switch from SHA-512 to BLAKE3 BLAKE3 is designed to be a very high performance cryptographic hash. The BLAKE3 team has shown 8.5x higher single-thread performance than SHA-512 on modern server hardware (AWS `c5.metal`). This change did not result in a significant improvement to my observed local build times, but newer hardware may see a meaningful improvement. Signed-off-by: George Hahn <george.hahn.vhs@gmail.com>
2020-01-17 09:29:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "e9ff35b701f3914bdb8fad3368d822c766ef2858b2583198e41639b936f09d3f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"arrayref",
"arrayvec",
"cc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"constant_time_eq",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"crypto-mac 0.8.0",
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"digest",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update deps.
2019-12-10 00:17:20 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "block-buffer"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.9.0"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "4152116fd6e9dadb291ae18fc1ec3575ed6d84c29642d97890f4b4a3417297e4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"generic-array",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "blocking"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c5e170dbede1f740736619b776d7251cb1b9095c435c34d8ca9f57fcd2f335e9"
dependencies = [
"async-channel",
"async-task",
"atomic-waker",
"fastrand",
"futures-lite",
"once_cell",
]
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
[[package]]
name = "boxfnonce"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5988cb1d626264ac94100be357308f29ff7cbdd3b36bda27f450a4ee3f713426"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "buf_redux"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
version = "0.8.4"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
checksum = "b953a6887648bb07a535631f2bc00fbdb2a2216f135552cb3f534ed136b9c07f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"memchr",
"safemem",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
[[package]]
name = "bufstream"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
version = "0.1.4"
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "40e38929add23cdf8a366df9b0e088953150724bcbe5fc330b0d8eb3b328eec8"
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "bumpalo"
version = "3.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2e8c087f005730276d1096a652e92a8bacee2e2472bcc9715a74d2bec38b5820"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
[[package]]
name = "byteorder"
cargo update
2020-04-28 07:55:50 +03:00
version = "1.3.4"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "08c48aae112d48ed9f069b33538ea9e3e90aa263cfa3d1c24309612b1f7472de"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Update to using the new tokio-io crate This is an abstraction of the Tokio stack now and doesn't have much impact on sccache itself but I figured it'd be good to update a few deps and pick up the recent version of things! Plus that and I'd like to start using the length_delimited module soon...
2017-03-09 21:00:18 +03:00
[[package]]
name = "bytes"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.4.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "206fdffcfa2df7cbe15601ef46c813fce0965eb3286db6b56c583b814b51c81c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
"either",
"iovec",
]
Update deps.
2019-12-10 00:17:20 +03:00
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "bytes"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.6"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "0e4cec68f03f32e44924783795810fa50a7035d8c8ebe78580ad7e6c703fba38"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
Run `cargo update`
2021-01-08 10:26:06 +03:00
[[package]]
name = "bytes"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ad1f8e949d755f9d79112b5bb46938e0ef9d3804a0b16dfab13aafcaa5f0fa72"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
[[package]]
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
name = "cache-padded"
version = "1.1.1"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
checksum = "631ae5198c9be5e753e5cc215e1bd73c2b466a3565173db433f52bb9d3e66dba"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
Depend on tokio-serde-bincode from crates.io
2017-07-13 21:33:57 +03:00
[[package]]
name = "case"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "e88b166b48e29667f5443df64df3c61dc07dc2b1a0b0d231800e07f09a33ecc1"
Depend on tokio-serde-bincode from crates.io
2017-07-13 21:33:57 +03:00
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
[[package]]
name = "cc"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.0.66"
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "4c0496836a84f8d0495758516b8621a622beb77c0fed418570e50764093ced48"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
dependencies = [
"jobserver",
]
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "cfg-if"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
version = "0.1.10"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "chrono"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.4.19"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"libc",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"num-integer",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"num-traits 0.2.14",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"time",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "chunked_transfer"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "498d20a7aaf62625b9bf26e637cf7736417cde1d0c99f1d04d1170229a85cf87"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "clap"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "2.33.3"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "37e58ac78573c40708d45522f0d80fa2f01cc4f9b4e2bf749807255454312002"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"ansi_term",
"atty",
"bitflags",
"strsim",
"textwrap",
"unicode-width",
"vec_map",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
[[package]]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bitflags",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "combine"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "4.5.2"
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "cc4369b5e4c0cddf64ad8981c0111e7df4f7078f4d6ba98fb31f2e17c4c57b7e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"bytes 0.5.6",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"bytes 1.0.0",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"futures-util",
"memchr",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"pin-project-lite 0.2.1",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"tokio 0.2.24",
]
[[package]]
name = "concurrent-queue"
version = "1.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "30ed07550be01594c6026cff2a1d7fe9c8f683caa798e12b68694ac9e88286a3"
dependencies = [
"cache-padded",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
[[package]]
name = "conhash"
chore: Update memcached to 0.3
2018-08-28 15:42:57 +03:00
version = "0.4.0"
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "99d6364d028778d0d98b6014fa5882da377cd10d3492b7734d266a428e9b1fca"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"md5",
]
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
Update deps.
2019-12-10 00:17:20 +03:00
name = "constant_time_eq"
Switch from SHA-512 to BLAKE3 BLAKE3 is designed to be a very high performance cryptographic hash. The BLAKE3 team has shown 8.5x higher single-thread performance than SHA-512 on modern server hardware (AWS `c5.metal`). This change did not result in a significant improvement to my observed local build times, but newer hardware may see a meaningful improvement. Signed-off-by: George Hahn <george.hahn.vhs@gmail.com>
2020-01-17 09:29:27 +03:00
version = "0.1.5"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "245097e9a4535ee1e3e3931fcfcd55a796a44c643e8596ff6566d68f09b87bbc"
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "cookie"
version = "0.12.0"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "888604f00b3db336d2af898ec3c1d5d0ddf5e6d462220f2ededc33a87ac4bbd5"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"time",
"url 1.7.2",
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
Update deps.
2019-12-10 00:17:20 +03:00
name = "cookie_store"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "46750b3f362965f197996c4448e4a0935e791bf7d6631bfce9ee0af3d24c919c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"cookie",
"failure",
"idna 0.1.5",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"publicsuffix",
"serde",
"serde_json",
"time",
"try_from",
"url 1.7.2",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "core-foundation"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.9.1"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "0a89e2ae426ea83155dccf10c0fa6b1463ef6d5fcb44cee0b224a408fa640a62"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"core-foundation-sys",
"libc",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "core-foundation-sys"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.8.2"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "ea221b5284a47e40033bf9b66f35f984ec0ea2931eb03505246cd27a963f981b"
Update deps.
2019-12-10 00:17:20 +03:00
Use the counted_array macro for the ARGS arrays One of the most annoying thing from using static arrays in rust is that there is no size inference, and you end up having to give the proper size. Which makes updates to the arrays cumbersome. I was reading "This Week in Rust 252", which linked to (RFC: Elide array size)[https://github.com/rust-lang/rfcs/pull/2545], set to address this very problem, and @durka linked to his counted-arrays crate, which already existed and essentially implements the idea behind the RFC.
2018-09-19 07:33:52 +03:00
[[package]]
name = "counted-array"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "384f8c53175c890920b6e0127b730709d2a173ca6c4dfdc81618ac9b46f648fe"
Use the counted_array macro for the ARGS arrays One of the most annoying thing from using static arrays in rust is that there is no size inference, and you end up having to give the proper size. Which makes updates to the arrays cumbersome. I was reading "This Week in Rust 252", which linked to (RFC: Elide array size)[https://github.com/rust-lang/rfcs/pull/2545], set to address this very problem, and @durka linked to his counted-arrays crate, which already existed and essentially implements the idea behind the RFC.
2018-09-19 07:33:52 +03:00
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
[[package]]
name = "cpuid-bool"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8aebca1129a03dc6dc2b127edd729435bbc4a37e1d5f4d7513165089ceb02634"
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
[[package]]
name = "crc32fast"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.2.1"
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "81156fece84ab6a9f2afdb109ce3ae577e42b1228441eded99bd77f627953b1a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "crossbeam-deque"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.7.3"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "9f02af974daeee82218205558e51ec8768b48cf524bd01d550abe5573a608285"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"crossbeam-epoch",
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
"maybe-uninit",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "crossbeam-epoch"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.8.2"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "058ed274caafc1f60c4997b5fc07bf7dc7cca454af7c6e81edffe5f33f70dace"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
"cfg-if 0.1.10",
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"lazy_static",
cargo update
2020-04-28 07:55:50 +03:00
"maybe-uninit",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"memoffset",
"scopeguard",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "crossbeam-queue"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7c979cd6cfe72335896575c6b5688da489e420d36a27a0b9eb0c73db574b4a4b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"crossbeam-utils 0.6.6",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
cargo update
2020-04-28 07:55:50 +03:00
[[package]]
name = "crossbeam-queue"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.2.3"
cargo update
2020-04-28 07:55:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "774ba60a54c213d409d5353bda12d49cd68d14e45036a285234c8d6f91f92570"
cargo update
2020-04-28 07:55:50 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
`cargo update`
2020-06-11 04:40:05 +03:00
"maybe-uninit",
cargo update
2020-04-28 07:55:50 +03:00
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "crossbeam-utils"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
version = "0.6.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "04973fa96e96579258a5091af6003abde64af786b860f18622b82e026cca60e6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"lazy_static",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "crossbeam-utils"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.7.2"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "c3c7c73a2d1e9fc0886a08b93e98eb643461230d5f1925e4036204d5f2e261a8"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
"cfg-if 0.1.10",
"lazy_static",
]
[[package]]
name = "crossbeam-utils"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "02d96d1e189ef58269ebe5b97953da3274d83a93af647c2ddd6f9dab28cedb8d"
dependencies = [
"autocfg 1.0.1",
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"lazy_static",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "crypto-mac"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.8.0"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "b584a330336237c1eecd3e94266efb216c56ed91225d634cb2991c5f3fd1aeab"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"generic-array",
"subtle",
Run `cargo update`
2020-12-08 08:07:09 +03:00
]
[[package]]
name = "crypto-mac"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.10.0"
Run `cargo update`
2020-12-08 08:07:09 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "4857fd85a0c34b3c3297875b747c1e02e06b6a0ea32dd892d8192b9ce0813ea6"
Run `cargo update`
2020-12-08 08:07:09 +03:00
dependencies = [
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"generic-array",
"subtle",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
daemonize the server process on unix
2016-10-26 23:22:52 +03:00
[[package]]
name = "daemonize"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
version = "0.4.1"
daemonize the server process on unix
2016-10-26 23:22:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
checksum = "70c24513e34f53b640819f0ac9f705b673fcf4006d7aab8778bee72ebfc89815"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"boxfnonce",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
]
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
Depend on tokio-serde-bincode from crates.io
2017-07-13 21:33:57 +03:00
[[package]]
name = "derive-error"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "629f1bb3abce791912ca85a24676fff54464f7deb122906adabc90fb96e876d3"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"case",
"quote 0.3.15",
"syn 0.11.11",
]
Depend on tokio-serde-bincode from crates.io
2017-07-13 21:33:57 +03:00
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
[[package]]
name = "difference"
Update assert_cli and tweak some of the tests using it. Also silence a lint warning from error-chain.
2018-07-26 17:16:55 +03:00
version = "2.0.0"
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "524cbf6897b527295dff137cec09ecf3a05f4fddffd7dfcd1585403449e74198"
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "digest"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
dependencies = [
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"generic-array",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
Replace `app_dirs` crate with `directories`. Fixes #233. The `app_dirs` crate has become unmaintained and is broken on macOS with Rust 1.25. The `directories` crate provides the same functionality and is maintained, so switch to using that instead.
2018-03-21 15:52:55 +03:00
[[package]]
name = "directories"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
version = "3.0.1"
Replace `app_dirs` crate with `directories`. Fixes #233. The `app_dirs` crate has become unmaintained and is broken on macOS with Rust 1.25. The `directories` crate provides the same functionality and is maintained, so switch to using that instead.
2018-03-21 15:52:55 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
checksum = "f8fed639d60b58d0f53498ab13d26f621fd77569cc6edb031f4cc36a2ad9da0f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"dirs-sys",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "dirs"
version = "1.0.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "3fd78930633bd1c6e35c4b42b1df7b0cbc6bc191146e512bb3bedf243fcc3901"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
"redox_users",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace `app_dirs` crate with `directories`. Fixes #233. The `app_dirs` crate has become unmaintained and is broken on macOS with Rust 1.25. The `directories` crate provides the same functionality and is maintained, so switch to using that instead.
2018-03-21 15:52:55 +03:00
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
[[package]]
name = "dirs-sys"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8e93d7f5705de3e49895a2b5e0b8855a1c27f080192ae9c32a6432d50741a57a"
dependencies = [
"libc",
"redox_users",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
]
update test harness crates This patch looks like a routine crate version update, but it fixes something very fundamentally wrong with the tests: `escargot`, to find the `sccache` binary during tests, would actually run `cargo build` and parse the output. There were all manner of hacks to try and build the binary with the correct set of features, none of which were reliable, and the hacks were not reliably present in all places, either. When the hacks were not present, `escargot` would rebuild the entire sccache crate, which was responsible for the `sccache_cargo` test taking entirely too long. When the hacks failed utterly, perfectly fine patches would mysteriously fail, as seen in #774. We can get rid of `escargot` because `assert-cmd` has been updated to a) not use `escargot` under the hood; and b) do something smarter to locate the target binary. The upshot is fewer mysterious test failures and significantly faster running tests.
2020-06-05 01:34:11 +03:00
[[package]]
name = "doc-comment"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fea41bba32d969b513997752735605054bc0dfa92b4c56bf1189f2e174be7a10"
switch back to released version of which, switch to a rusoto branch with a bug fix
2016-08-08 22:06:06 +03:00
[[package]]
name = "dtoa"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.4.7"
switch back to released version of which, switch to a rusoto branch with a bug fix
2016-08-08 22:06:06 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "88d7ed2934d741c6b37e33e3832298e8850b53fd2d2bea03873375596c7cea4e"
switch back to released version of which, switch to a rusoto branch with a bug fix
2016-08-08 22:06:06 +03:00
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
[[package]]
name = "either"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.6.1"
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "e78d4f1cc4ae33bbfc157ed5d5a5ef3bc29227303d595861deb238fcec4e9457"
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "encoding_rs"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.8.26"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "801bbab217d7f79c0062f4f7205b5d4427c6d1a7bd7aafdd1475f7c59d62b283"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "env_logger"
Upgrade env_logger to 0.8
2020-12-10 01:51:36 +03:00
version = "0.8.2"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade env_logger to 0.8
2020-12-10 01:51:36 +03:00
checksum = "f26ecb66b4bdca6c1409b40fb255eefc2bd4f6d135dab3c3124f80ffa2a9661e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"atty",
"humantime",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"regex",
"termcolor",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
[[package]]
name = "error-chain"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.12.4"
Ignore CARGO_MAKEFLAGS when calculating Rust hash keys. Fixes #193 Since cargo gained jobserver support it now passes a CARGO_MAKEFLAGS environment variable which is different for every build (it contains file descriptor numbers or semaphore values). sccache uses all environment variables starting with `CARGO_` as inputs to the hash key for Rust compilation so this broke things. I think it was mostly only a problem on Windows, where the values were semaphores. On POSIX platforms the values are file descriptors, which are probably likely to be the same between runs of cargo. This change also adds a test for compiling a simple Rust crate with cargo and verifying that we get a cache hit. I pulled in the `assert_cli` crate to write that test, which worked nicely.
2017-10-25 21:09:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "2d2f06b9cac1506ece98fe3231e3cc9c4410ec3d5b1f24ae1c8946f0742cdefc"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
`cargo update`
2020-06-11 04:40:05 +03:00
"version_check 0.9.2",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update assert_cli and tweak some of the tests using it. Also silence a lint warning from error-chain.
2018-07-26 17:16:55 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "event-listener"
version = "2.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7531096570974c3a9dcf9e4b8e1cede1ec26cf5046219fb3b9d897503b9be59"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
[[package]]
name = "failure"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.1.8"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "d32e9bd16cc02eae7db7ef620b392808b89f6a5e16bb3497d159c6b92a0f4f86"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"backtrace",
"failure_derive",
]
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
[[package]]
name = "failure_derive"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.1.8"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "aa4da3c766cd7a0db8242e326e9e4e081edd567072893ed320008189715366a4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"synstructure",
]
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "fastrand"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca5faf057445ce5c9d4329e382b2ce7ca38550ef3b73a5348362d5f24e0c7fe3"
dependencies = [
"instant",
]
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
[[package]]
name = "filetime"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.13"
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "0c122a393ea57648015bf06fbd3d372378992e86b9ff5a7a497b076a28c79efe"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
"redox_syscall",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
[[package]]
name = "flate2"
Don't enable deflate on the zip crate It's not needed since be9da57. This allows to update the flate2 crate for reqwest.
2020-12-08 10:54:34 +03:00
version = "1.0.19"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Don't enable deflate on the zip crate It's not needed since be9da57. This allows to update the flate2 crate for reqwest.
2020-12-08 10:54:34 +03:00
checksum = "7411863d55df97a419aa64cb4d2f167103ea9d767e2c54a1868b7ac3f6b47129"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Don't enable deflate on the zip crate It's not needed since be9da57. This allows to update the flate2 crate for reqwest.
2020-12-08 10:54:34 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"crc32fast",
"libc",
Don't enable deflate on the zip crate It's not needed since be9da57. This allows to update the flate2 crate for reqwest.
2020-12-08 10:54:34 +03:00
"miniz_oxide",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
[[package]]
name = "float-cmp"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.8.0"
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "e1267f4ac4f343772758f7b1bdcbe767c218bbab93bb432acbf5162bbf85a6c4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"num-traits 0.2.14",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "fnv"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "1.0.7"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
[[package]]
name = "foreign-types"
Update ring
2018-01-07 18:33:04 +03:00
version = "0.3.2"
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"foreign-types-shared",
]
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
Don't block sending compile result to client on cache write. Fixes #19. This change makes `get_cached_or_compile` return a `Future` for the cache write instead of blocking on it. The server then waits for the result on a thread. It also changes the server to record cache write timings, and display the average in the stats.
2016-11-03 00:15:14 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "foreign-types-shared"
version = "0.1.1"
Don't block sending compile result to client on cache write. Fixes #19. This change makes `get_cached_or_compile` return a `Future` for the cache write instead of blocking on it. The server then waits for the result on a thread. It also changes the server to record cache write timings, and display the average in the stats.
2016-11-03 00:15:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
Don't block sending compile result to client on cache write. Fixes #19. This change makes `get_cached_or_compile` return a `Future` for the cache write instead of blocking on it. The server then waits for the result on a thread. It also changes the server to record cache write timings, and display the average in the stats.
2016-11-03 00:15:14 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "form_urlencoded"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ece68d15c92e84fa4f19d3780f1294e5ca82a78a6d515f1efaabcc144688be00"
dependencies = [
"matches",
"percent-encoding 2.1.0",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "fuchsia-cprng"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
Update deps.
2019-12-10 00:17:20 +03:00
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "fuchsia-zircon"
version = "0.3.3"
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bitflags",
"fuchsia-zircon-sys",
]
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "fuchsia-zircon-sys"
version = "0.3.3"
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "futures"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.30"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "4c7e4c2612746b0df8fed4ce0c69156021b704c9aefa360311c04e6e9e002eed"
Update ring
2018-01-07 18:33:04 +03:00
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
[[package]]
name = "futures"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "c70be434c505aee38639abccb918163b63158a4b4bb791b45b7023044bdc3c9c"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
dependencies = [
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-channel"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "f01c61843314e95f96cc9245702248733a3a3d744e43e2e755e3c7af8348a0a9"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
dependencies = [
"futures-core",
"futures-sink",
]
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "futures-core"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "db8d3b0917ff63a2a96173133c02818fac4a746b0a57569d3baca9ec0e945e08"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "futures-cpupool"
version = "0.1.8"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ab90cde24b3319636588d0c35fe03b1333857621051837ed769faefb4c2162e4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"num_cpus",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
[[package]]
name = "futures-executor"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "9ee9ca2f7eb4475772cf39dd1cd06208dce2670ad38f4d9c7262b3e15f127068"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
dependencies = [
"futures-core",
"futures-task",
"futures-util",
Switch from futures_cpupool::CpuPool to futures_03::executor::ThreadPool
2020-06-12 12:01:49 +03:00
"num_cpus",
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
]
[[package]]
name = "futures-io"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "e37c1a51b037b80922864b8eed90692c5cd8abd4c71ce49b77146caa47f3253b"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "futures-lite"
version = "1.11.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4481d0cd0de1d204a4fa55e7d45f07b1d958abcb06714b3446438e2eff695fb"
dependencies = [
"fastrand",
"futures-core",
"futures-io",
"memchr",
"parking",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"pin-project-lite 0.2.1",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"waker-fn",
]
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
[[package]]
name = "futures-macro"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "0f8719ca0e1f3c5e34f3efe4570ef2c0610ca6da85ae7990d472e9cbfba13664"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
dependencies = [
"proc-macro-hack",
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
]
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "futures-sink"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "f6adabac1290109cfa089f79192fb6244ad2c3f1cc2281f3e1dd987592b71feb"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "futures-task"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "a92a0843a2ff66823a8f7c77bffe9a09be2b64e533562c412d63075643ec0038"
`cargo update`
2020-06-11 04:40:05 +03:00
dependencies = [
"once_cell",
]
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "futures-util"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.3.9"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "036a2107cdeb57f6d7322f1b6c363dad67cd63ca3b7d1b925bdf75bd5d96cda9"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
"futures-channel",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"futures-core",
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
"futures-io",
"futures-macro",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"futures-sink",
"futures-task",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"memchr",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"pin-project-lite 0.2.1",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"pin-utils",
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
"proc-macro-hack",
"proc-macro-nested",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"slab",
]
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "generic-array"
version = "0.14.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "501466ecc8a30d1d3b7fc9229b122b2ce8ed6e9d9223f1138d4babb253e51817"
dependencies = [
"typenum",
"version_check 0.9.2",
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
[[package]]
name = "getopts"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.2.21"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "14dbbfd5c71d70241ecf9e6f13737f7b5ce823821063188d7e46c41d371eebd5"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"unicode-width",
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
update jobserver crate version This change should help #578 not cause errors on the linux64 musl target...though why that target isn't failing *now*, with the older version of `jobserver` that we have, is something I don't understand
2019-11-04 19:05:43 +03:00
[[package]]
name = "getrandom"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.1.16"
update jobserver crate version This change should help #578 not cause errors on the linux64 musl target...though why that target isn't failing *now*, with the older version of `jobserver` that we have, is something I don't understand
2019-11-04 19:05:43 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2021-01-08 10:26:06 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"wasi 0.9.0+wasi-snapshot-preview1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
update jobserver crate version This change should help #578 not cause errors on the linux64 musl target...though why that target isn't failing *now*, with the older version of `jobserver` that we have, is something I don't understand
2019-11-04 19:05:43 +03:00
`cargo update`
2020-06-11 04:40:05 +03:00
[[package]]
name = "gimli"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.23.0"
`cargo update`
2020-06-11 04:40:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "f6503fe142514ca4799d4c26297c4248239fe8838d827db6bd6065c6ed29a6ce"
`cargo update`
2020-06-11 04:40:05 +03:00
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
[[package]]
name = "glob"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "gloo-timers"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "47204a46aaff920a1ea58b11d03dec6f704287d27561724a4631e450654a891f"
dependencies = [
"futures-channel",
"futures-core",
"js-sys",
"wasm-bindgen",
"web-sys",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "h2"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.26"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "a5b34c246847f938a410a03c5458c7fee2274436675e76d8b903c08efc29c462"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"fnv",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"http",
"indexmap",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"slab",
"string",
"tokio-io",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "hashbrown"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d7afe4a420e3fe79967a00898cc1f4db7c8a49a9333a29f8a4bd76a253d5cd04"
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "hermit-abi"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.17"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "5aca5565f760fb5b220e499d72710ed156fdb74e631659e99377d9ebfbd13ae8"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
]
Update deps.
2019-12-10 00:17:20 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "hmac"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.10.1"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "c1441c6b1e930e2817404b5046f1f989899143a12bf92de603b69f4e0aee1e15"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"crypto-mac 0.10.0",
"digest",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "http"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.21"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "d6ccf5ede3a895d8856620237b2f02972c1bbc78d2965ad7fe8838d4a0ed41f0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"fnv",
"itoa",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
[[package]]
name = "http-body"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "6741c859c1b2463a423a1dbce98d418e6c3c3fc720fb0d45528657320920292d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"http",
"tokio-buf",
]
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "httparse"
Update deps.
2019-12-10 00:17:20 +03:00
version = "1.3.4"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "cd179ae861f0c2e53da70d892f5f3029f9594be0c41dc5269cd371691b1dc2f9"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
[[package]]
name = "humantime"
Upgrade env_logger to 0.8
2020-12-10 01:51:36 +03:00
version = "2.0.1"
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade env_logger to 0.8
2020-12-10 01:51:36 +03:00
checksum = "3c1ad908cc71012b7bea4d0c53ba96a8cba9962f048fa68d143376143d863b7a"
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "hyper"
Update the minimum set of deps for cargo audit cargo audit now reports 0 vulnerabilities down from 3
2021-05-12 02:08:35 +03:00
version = "0.12.36"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update the minimum set of deps for cargo audit cargo audit now reports 0 vulnerabilities down from 3
2021-05-12 02:08:35 +03:00
checksum = "5c843caf6296fc1f93444735205af9ed4e109a539005abb2564ae1d6fad34c52"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"futures-cpupool",
"h2",
"http",
"http-body",
"httparse",
"iovec",
"itoa",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"net2",
"rustc_version",
"time",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"tokio 0.1.22",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-buf",
"tokio-executor",
"tokio-io",
"tokio-reactor",
"tokio-tcp",
"tokio-threadpool",
"tokio-timer",
"want",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "hyper-tls"
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
version = "0.3.2"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "3a800d6aa50af4b5850b2b0f659625ce9504df908e9733b635720483be26174f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"hyper",
"native-tls",
"tokio-io",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "hyperx"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "78e2d2253d7a17929560fc3adf48c48fc924c94fa4507e037a60e6bc55c0eda6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"base64 0.9.3",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"http",
"httparse",
"language-tags",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
cargo update
2020-04-28 07:55:50 +03:00
"mime 0.3.16",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"percent-encoding 1.0.1",
"time",
"unicase 2.6.0",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "idna"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
version = "0.1.5"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "38f09e0f0b1fb55fdee1f17470ad800da77af5186a1a76c026b679358b7e844e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"matches",
"unicode-bidi",
"unicode-normalization",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "idna"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "02e2673c30ee86b5b96a9cb52ad15718aa1f966f5ab9ad54a8b95d5ca33120a9"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"matches",
"unicode-bidi",
"unicode-normalization",
]
Update to using the new tokio-io crate This is an abstraction of the Tokio stack now and doesn't have much impact on sccache itself but I figured it'd be good to update a few deps and pick up the recent version of things! Plus that and I'd like to start using the length_delimited module soon...
2017-03-09 21:00:18 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "indexmap"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "1.6.1"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "4fb1fa934250de4de8aef298d81c729a7d33d8c239daa3a7575e6b92bfc7313b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
"hashbrown",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "instant"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "61124eeebbd69b8190558df225adf7e4caafce0d743919e5d6b19652314ec5ec"
dependencies = [
"cfg-if 1.0.0",
]
Update to using the new tokio-io crate This is an abstraction of the Tokio stack now and doesn't have much impact on sccache itself but I figured it'd be good to update a few deps and pick up the recent version of things! Plus that and I'd like to start using the length_delimited module soon...
2017-03-09 21:00:18 +03:00
[[package]]
name = "iovec"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.4"
Update to using the new tokio-io crate This is an abstraction of the Tokio stack now and doesn't have much impact on sccache itself but I figured it'd be good to update a few deps and pick up the recent version of things! Plus that and I'd like to start using the length_delimited module soon...
2017-03-09 21:00:18 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "b2b3ea6ff95e175473f8ffe6a7eb7c00d054240321b84c57051175fe3c1e075e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
[[package]]
name = "itertools"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
version = "0.9.0"
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
checksum = "284f18f85651fe11e8a991b2adb42cb078325c996ed026d994719efcfca1d54b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"either",
]
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
Upgrade itertools to 0.10
2021-01-08 10:28:43 +03:00
[[package]]
name = "itertools"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "37d572918e350e82412fe766d24b15e6682fb2ed2bbe018280caa810397cb319"
dependencies = [
"either",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "itoa"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.4.7"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "dd25036021b0de88a0aff6b850051563c6516d0bf53f8638938edbb9de732736"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Add jobserver support to sccache This commit alters the main sccache server to operate and orchestrate its own GNU make style jobserver. This is primarily intended for interoperation with rustc itself. The Rust compiler currently has a multithreaded mode where it will execute code generation and optimization on the LLVM side of things in parallel. This parallelism, however, can overload a machine quickly if not properly accounted for (e.g. if 10 rustcs all spawn 10 threads...). The usage of a GNU make style jobserver is intended to arbitrate and rate limit all these rustc instances to ensure that one build's maximal parallelism never exceeds a particular amount. Currently for Rust Cargo is the primary driver for setting up a jobserver. Cargo will create this and manage this per compilation, ensuring that any one `cargo build` invocation never exceeds a maximal parallelism. When sccache enters the picture, however, the story gets slightly more odd. The jobserver implementation on Unix relies on inheritance of file descriptors in spawned processes. With sccache, however, there's no inheritance as the actual rustc invocation is spawned by the server, not the client. In this case the env vars used to configure the jobsever are usually incorrect. To handle this problem this commit bakes a jobserver directly into sccache itself. The jobserver then overrides whatever jobserver the client has configured in its own env vars to ensure correct operation. The settings of each jobserver may be misconfigured (there's no way to configure sccache's jobserver right now), but hopefully that's not too much of a problem for the forseeable future. The implementation here was to provide a thin wrapper around the `jobserver` crate with a futures-based interface. This interface was then hooked into the mock command infrastructure to automatically acquire a jobserver token when spawning a process and automatically drop the token when the process exits. Additionally, all spawned processes will now automatically receive a configured jobserver. cc rust-lang/rust#42867, the original motivation for this commit
2017-09-27 19:14:51 +03:00
[[package]]
name = "jobserver"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.21"
Add jobserver support to sccache This commit alters the main sccache server to operate and orchestrate its own GNU make style jobserver. This is primarily intended for interoperation with rustc itself. The Rust compiler currently has a multithreaded mode where it will execute code generation and optimization on the LLVM side of things in parallel. This parallelism, however, can overload a machine quickly if not properly accounted for (e.g. if 10 rustcs all spawn 10 threads...). The usage of a GNU make style jobserver is intended to arbitrate and rate limit all these rustc instances to ensure that one build's maximal parallelism never exceeds a particular amount. Currently for Rust Cargo is the primary driver for setting up a jobserver. Cargo will create this and manage this per compilation, ensuring that any one `cargo build` invocation never exceeds a maximal parallelism. When sccache enters the picture, however, the story gets slightly more odd. The jobserver implementation on Unix relies on inheritance of file descriptors in spawned processes. With sccache, however, there's no inheritance as the actual rustc invocation is spawned by the server, not the client. In this case the env vars used to configure the jobsever are usually incorrect. To handle this problem this commit bakes a jobserver directly into sccache itself. The jobserver then overrides whatever jobserver the client has configured in its own env vars to ensure correct operation. The settings of each jobserver may be misconfigured (there's no way to configure sccache's jobserver right now), but hopefully that's not too much of a problem for the forseeable future. The implementation here was to provide a thin wrapper around the `jobserver` crate with a futures-based interface. This interface was then hooked into the mock command infrastructure to automatically acquire a jobserver token when spawning a process and automatically drop the token when the process exits. Additionally, all spawned processes will now automatically receive a configured jobserver. cc rust-lang/rust#42867, the original motivation for this commit
2017-09-27 19:14:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "5c71313ebb9439f74b00d9d2dcec36440beaf57a6aa0623068441dd7cd81a7f2"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
]
Add jobserver support to sccache This commit alters the main sccache server to operate and orchestrate its own GNU make style jobserver. This is primarily intended for interoperation with rustc itself. The Rust compiler currently has a multithreaded mode where it will execute code generation and optimization on the LLVM side of things in parallel. This parallelism, however, can overload a machine quickly if not properly accounted for (e.g. if 10 rustcs all spawn 10 threads...). The usage of a GNU make style jobserver is intended to arbitrate and rate limit all these rustc instances to ensure that one build's maximal parallelism never exceeds a particular amount. Currently for Rust Cargo is the primary driver for setting up a jobserver. Cargo will create this and manage this per compilation, ensuring that any one `cargo build` invocation never exceeds a maximal parallelism. When sccache enters the picture, however, the story gets slightly more odd. The jobserver implementation on Unix relies on inheritance of file descriptors in spawned processes. With sccache, however, there's no inheritance as the actual rustc invocation is spawned by the server, not the client. In this case the env vars used to configure the jobsever are usually incorrect. To handle this problem this commit bakes a jobserver directly into sccache itself. The jobserver then overrides whatever jobserver the client has configured in its own env vars to ensure correct operation. The settings of each jobserver may be misconfigured (there's no way to configure sccache's jobserver right now), but hopefully that's not too much of a problem for the forseeable future. The implementation here was to provide a thin wrapper around the `jobserver` crate with a futures-based interface. This interface was then hooked into the mock command infrastructure to automatically acquire a jobserver token when spawning a process and automatically drop the token when the process exits. Additionally, all spawned processes will now automatically receive a configured jobserver. cc rust-lang/rust#42867, the original motivation for this commit
2017-09-27 19:14:51 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "js-sys"
version = "0.3.46"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cf3d7383929f7c9c7c2d0fa596f325832df98c3704f2c60553080f7127a58175"
dependencies = [
"wasm-bindgen",
]
Implement GCS backend
2017-05-06 03:02:48 +03:00
[[package]]
name = "jsonwebtoken"
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
version = "7.2.0"
Replace usage of jsonwebtoken for gcs Rebase cleanup
2019-10-31 20:57:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
checksum = "afabcc15e437a6484fc4f12d0fd63068fe457bf93f1c148d3d9649c60b103f32"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"base64 0.12.3",
"pem",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"ring",
"serde",
"serde_json",
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"simple_asn1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Implement GCS backend
2017-05-06 03:02:48 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"winapi 0.2.8",
"winapi-build",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "kv-log-macro"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0de8b303297635ad57c9f5059fd9cee7a47f8e8daa09df0fcd07dd39fb22977f"
dependencies = [
"log 0.4.11",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "language-tags"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "a91d884b6667cd606bb5a69aa0c99ba811a115fc68915e7056ec08a46e93199a"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "lazy_static"
Update deps.
2019-12-10 00:17:20 +03:00
version = "1.4.0"
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "libc"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.2.82"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "89203f3fba0a3795506acaad8ebce3c80c0af93f994d5a1d7a0b1eeb23271929"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
[[package]]
name = "libmount"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.15"
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "23c4c2ad2d5cbd2f5a05620c3daf45930add53ec207fa99ce5eec971089dc35f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
"nix 0.14.1",
"quick-error",
]
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
Make DiskCache limit the size of the on-disk cache by using LruDiskCache. Fixes #29
2016-11-29 03:59:42 +03:00
[[package]]
name = "linked-hash-map"
update linked-hash-map for lru-disk-cache: 0.2 -> 0.5
2020-07-14 13:30:20 +03:00
version = "0.5.3"
Make DiskCache limit the size of the on-disk cache by using LruDiskCache. Fixes #29
2016-11-29 03:59:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update linked-hash-map for lru-disk-cache: 0.2 -> 0.5
2020-07-14 13:30:20 +03:00
checksum = "8dd5a6d5999d9907cda8ed67bbd137d3af8085216c2ac62de5be860bd41f304a"
Make DiskCache limit the size of the on-disk cache by using LruDiskCache. Fixes #29
2016-11-29 03:59:42 +03:00
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
[[package]]
name = "local-encoding"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "e1ceb20f39ff7ae42f3ff9795f3986b1daad821caaa1e1732a0944103a5a1a66"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"kernel32-sys",
"skeptic",
"winapi 0.2.8",
]
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "lock_api"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.3.4"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "c4da24a77a3d8a6d4862d95f72e6fdb9c09a643ecdb402d754004a557f2bec75"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"scopeguard",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "log"
Update ring
2018-01-07 18:33:04 +03:00
version = "0.3.9"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "e19e8d5c34a3e0e2223db8e060f9e8264aeeb5c5fc64a4ee9965c062211c024b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Make DiskCache limit the size of the on-disk cache by using LruDiskCache. Fixes #29
2016-11-29 03:59:42 +03:00
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "log"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.4.11"
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "4fabed175da42fed1fa0746b0ea71f412aa9d35e76e95e59b192c64b9dc2bf8b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "matches"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
version = "0.1.8"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7ffc5c5338469d4d3ea17d269fa8ea3512ad247247c30bd2df69e68309ed0a08"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "maybe-uninit"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "60302e4db3a61da70c0cb7991976248362f30319e88850c487b9b95bbf059e00"
Update deps.
2019-12-10 00:17:20 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "md-5"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.9.1"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "7b5a279bb9607f9f53c22d496eade00d138d1bdcccd07d74650387cf94942a15"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"block-buffer",
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"digest",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"opaque-debug",
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
chore: Update memcached to 0.3
2018-08-28 15:42:57 +03:00
[[package]]
name = "md5"
version = "0.3.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "79c56d6a0b07f9e19282511c83fc5b086364cbae4ba8c7d5f190c3d9b0425a48"
chore: Update memcached to 0.3
2018-08-28 15:42:57 +03:00
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
[[package]]
name = "memcached-rs"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
version = "0.4.2"
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
checksum = "e3804643a8b556cd39d6b3ec5a181fdf36b642952d57f4c52bebd457d0ee0b1d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bufstream",
"byteorder",
"conhash",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"rand 0.7.3",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"semver",
"unix_socket",
]
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "memchr"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "2.3.4"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "0ee1c47aaa256ecabcaea351eae4a9b01ef39ed810004e298d2511ed284b1525"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "memoffset"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.6"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "043175f069eda7b85febe4a74abbaeff828d9f8b448515d3151a14a3542811aa"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "mime"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ba626b8a6de5da682e1caa06bdb42a335aee5a84db8e5046a3e8ab17ba0a3ae0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"log 0.3.9",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "mime"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.3.16"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "2a60c7ce501c71e03a9c9c0d35b861413ae925bd979cc7a4e30d060069aaac8d"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "mime_guess"
cargo update
2020-04-28 07:55:50 +03:00
version = "1.8.8"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "216929a5ee4dd316b1702eedf5e74548c123d370f47841ceaac38ca154690ca3"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"mime 0.2.6",
"phf",
"phf_codegen",
"unicase 1.4.2",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "mime_guess"
cargo update
2020-04-28 07:55:50 +03:00
version = "2.0.3"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "2684d4c2e97d99848d30b324b00c8fcc7e5c897b7cbb5819b09e7c90e8baf212"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"mime 0.3.16",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"unicase 2.6.0",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "miniz_oxide"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0f2d26ec3309788e423cfbf68ad1800f061638098d76a83681af979dc4eda19d"
dependencies = [
"adler",
"autocfg 1.0.1",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "mio"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.6.23"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "4afd66f5b91bf2a3bc13fad0e21caedac168ca4c707504e75585648ae80e4cc4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"fuchsia-zircon",
"fuchsia-zircon-sys",
"iovec",
"kernel32-sys",
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
"miow 0.2.2",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"net2",
"slab",
"winapi 0.2.8",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
[[package]]
name = "mio-named-pipes"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.7"
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "0840c1c50fd55e521b247f949c241c9997709f23bd7f023b9762cd561e935656"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"miow 0.3.6",
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
[[package]]
name = "mio-uds"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.6.8"
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "afcb699eb26d4332647cc848492bbc15eafb26f08d0304550d5aa1f612e066f0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"iovec",
"libc",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "miow"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.2"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "ebd808424166322d4a38da87083bfddd3ac4c131334ed55856112eb06d46944d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"kernel32-sys",
"net2",
"winapi 0.2.8",
"ws2_32-sys",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "miow"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.3.6"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "5a33c1b55807fbed163481b5ba66db4b2fa6cde694a5027be10fb724206c5897"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"socket2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update ring
2018-01-07 18:33:04 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "multipart"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
version = "0.15.4"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
checksum = "adba94490a79baf2d6a23eac897157047008272fa3eecb3373ae6377b91eca28"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"buf_redux",
"httparse",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"mime 0.2.6",
cargo update
2020-04-28 07:55:50 +03:00
"mime_guess 1.8.8",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"quick-error",
"rand 0.4.6",
"safemem",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tempdir",
"twoway",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "native-tls"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.2.7"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "b8d96b2e1c8da3957d58100b09f102c6d9cfdfced01b7ec5a8974044bb09dbd4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"lazy_static",
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "nb-connect"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8123a81538e457d44b933a02faf885d3fe8408806b23fa700e8f01c6c3a98998"
dependencies = [
"libc",
"winapi 0.3.9",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "net2"
Run `cargo update`
2020-12-10 03:19:32 +03:00
version = "0.2.37"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-10 03:19:32 +03:00
checksum = "391630d12b68002ae1e25e8f974306474966550ad82dac6886fb8910c19568ae"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
[[package]]
name = "nix"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
version = "0.14.1"
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
checksum = "6c722bee1037d430d0f8e687bbdbf222f27cc6e4e68d5caf630857bb2b6dbdce"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bitflags",
"cc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
"void",
]
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
Update deps.
2019-12-10 00:17:20 +03:00
name = "nix"
Upgrade nix to 0.19
2020-12-10 01:56:41 +03:00
version = "0.19.1"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade nix to 0.19
2020-12-10 01:56:41 +03:00
checksum = "b2ccba0cfe4fdf15982d1674c69b1fd80bad427d293849982668dfe454bd61f2"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bitflags",
"cc",
Upgrade nix to 0.19
2020-12-10 01:56:41 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "normalize-line-endings"
update test harness crates This patch looks like a routine crate version update, but it fixes something very fundamentally wrong with the tests: `escargot`, to find the `sccache` binary during tests, would actually run `cargo build` and parse the output. There were all manner of hacks to try and build the binary with the correct set of features, none of which were reliable, and the hacks were not reliably present in all places, either. When the hacks were not present, `escargot` would rebuild the entire sccache crate, which was responsible for the `sccache_cargo` test taking entirely too long. When the hacks failed utterly, perfectly fine patches would mysteriously fail, as seen in #774. We can get rid of `escargot` because `assert-cmd` has been updated to a) not use `escargot` under the hood; and b) do something smarter to locate the target binary. The upshot is fewer mysterious test failures and significantly faster running tests.
2020-06-05 01:34:11 +03:00
version = "0.3.0"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update test harness crates This patch looks like a routine crate version update, but it fixes something very fundamentally wrong with the tests: `escargot`, to find the `sccache` binary during tests, would actually run `cargo build` and parse the output. There were all manner of hacks to try and build the binary with the correct set of features, none of which were reliable, and the hacks were not reliably present in all places, either. When the hacks were not present, `escargot` would rebuild the entire sccache crate, which was responsible for the `sccache_cargo` test taking entirely too long. When the hacks failed utterly, perfectly fine patches would mysteriously fail, as seen in #774. We can get rid of `escargot` because `assert-cmd` has been updated to a) not use `escargot` under the hood; and b) do something smarter to locate the target binary. The upshot is fewer mysterious test failures and significantly faster running tests.
2020-06-05 01:34:11 +03:00
checksum = "61807f77802ff30975e01f4f071c8ba10c022052f98b3294119f3e615d13e5be"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "num-bigint"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "090c7f9998ee0ff65aa5b723e4009f7b217707f1fb5ea551329cc4d6231fb304"
dependencies = [
"autocfg 1.0.1",
"num-integer",
"num-traits 0.2.14",
]
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
[[package]]
name = "num-integer"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.44"
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "d2cc698a63b549a70bc047073d2949cce27cd1c7b0a4a862d08a8031bc2801db"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
"num-traits 0.2.14",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
[[package]]
name = "num-traits"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
version = "0.1.43"
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "92e5113e9fd4cc14ded8e499429f396a20f98c772a47cc8622a736e1ec843c31"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"num-traits 0.2.14",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
[[package]]
name = "num-traits"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.14"
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "num_cpus"
cargo update
2020-04-28 07:55:50 +03:00
version = "1.13.0"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"hermit-abi",
"libc",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
[[package]]
name = "number_prefix"
Upgrade number_prefix to 0.4
2020-12-10 02:03:49 +03:00
version = "0.4.0"
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade number_prefix to 0.4
2020-12-10 02:03:49 +03:00
checksum = "830b246a0e5f20af87141b25c173cd1b609bd7779a4617d6ec582abaf90870f3"
drop format_size code in favor of number_prefix crate
2016-05-12 22:46:22 +03:00
`cargo update`
2020-06-11 04:40:05 +03:00
[[package]]
name = "object"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.22.0"
`cargo update`
2020-06-11 04:40:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "8d3b63360ec3cb337817c2dbd47ab4a0f170d285d8e5a2064600f3def1402397"
`cargo update`
2020-06-11 04:40:05 +03:00
[[package]]
name = "once_cell"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.5.2"
`cargo update`
2020-06-11 04:40:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "13bd41f508810a131401606d54ac32a467c97172d74ba7662562ebba5ad07fa0"
`cargo update`
2020-06-11 04:40:05 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "opaque-debug"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.3.0"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "624a8340c38c1b80fd549087862da4ba43e08858af025b236e509b6649fc13d5"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
chore: Remove native_tls and tokio-tls and update openssl to 0.10
2018-08-28 15:25:42 +03:00
[[package]]
name = "openssl"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.10.32"
chore: Remove native_tls and tokio-tls and update openssl to 0.10
2018-08-28 15:25:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "038d43985d1ddca7a9900630d8cd031b56e4794eecc2e9ea39dd17aa04399a70"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bitflags",
Run `cargo update`
2020-12-10 03:19:32 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"foreign-types",
"lazy_static",
"libc",
"openssl-sys",
]
chore: Remove native_tls and tokio-tls and update openssl to 0.10
2018-08-28 15:25:42 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "openssl-probe"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
[[package]]
name = "openssl-sys"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.9.60"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "921fc71883267538946025deffb622905ecad223c28efbfdef9bb59a0175f3e6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"autocfg 1.0.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"cc",
"libc",
"pkg-config",
"vcpkg",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "parking"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "427c3892f9e783d91cc128285287e70a59e206ca452770ece88a76f7a3eddd72"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "parking_lot"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.9.0"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "f842b1982eb6c2fe34036a4fbfb06dd185a3f5c8edfaacdf7d1ea10b07de6252"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"lock_api",
"parking_lot_core",
"rustc_version",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "parking_lot_core"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.6.2"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "b876b1b9e7ac6e1a74a6da34d25c42e17e8862aa409cbbbdcfc8d86c6f3bc62b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"cloudabi",
"libc",
"redox_syscall",
"rustc_version",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"smallvec",
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "pem"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4c220d01f863d13d96ca82359d1e81e64a7c6bf0637bcde7b2349630addf0c6"
dependencies = [
"base64 0.13.0",
"once_cell",
"regex",
]
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
[[package]]
name = "percent-encoding"
Update ring
2018-01-07 18:33:04 +03:00
version = "1.0.1"
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "31010dd2e1ac33d5b46a5b413495239882813e0369f8ed8a5e266f173602f831"
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "percent-encoding"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
Update deps.
2019-12-10 00:17:20 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "phf"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.7.24"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "b3da44b85f8e8dfaec21adae67f95d93244b2ecf6ad2a692320598dcc8e6dd18"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"phf_shared",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "phf_codegen"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.7.24"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "b03e85129e324ad4166b06b2c7491ae27fe3ec353af72e72cd1654c7225d517e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"phf_generator",
"phf_shared",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "phf_generator"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.7.24"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "09364cc93c159b8b06b1f4dd8a4398984503483891b0c26b867cf431fb132662"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"phf_shared",
"rand 0.6.5",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "phf_shared"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.7.24"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "234f71a15de2288bcb7e3b6515828d22af7ec8598ee6d24c3b526fa0a80b67a0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"siphasher",
"unicase 1.4.2",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "pin-project-lite"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.11"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "c917123afa01924fc84bb20c4c03f004d9c38e5127e3c039bbf7f4b9c76a2f6b"
[[package]]
name = "pin-project-lite"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "0.2.1"
Run `cargo update`
2020-12-08 08:07:09 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "e36743d754ccdf9954c2e352ce2d4b106e024c814f6499c2dadff80da9a442d8"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
[[package]]
name = "pkg-config"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.3.19"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "3831453b3449ceb48b6d9c7ad7c96d5ea673e9b470a1dc578c2ce6521230884c"
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "polling"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2a7bc6b2a29e632e45451c941832803a18cce6781db04de8a04696cdca8bde4"
dependencies = [
"cfg-if 0.1.10",
"libc",
"log 0.4.11",
"wepoll-sys",
"winapi 0.3.9",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "ppv-lite86"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.10"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "ac74c624d6b2d21f425f752262f42188365d7b8ff1aff74c82e45136510a4857"
Update deps.
2019-12-10 00:17:20 +03:00
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
[[package]]
name = "predicates"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.6"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "73dd9b7b200044694dfede9edf907c1ca19630908443e9447e624993700c6932"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"difference",
"float-cmp",
"normalize-line-endings",
"predicates-core",
"regex",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "predicates-core"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.1"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "fb3dbeaaf793584e29c58c7e3a82bbb3c7c06b63cea68d13b0e3cddc124104dc"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "predicates-tree"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.1"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "aee95d988ee893cb35c06b148c80ed2cd52c8eea927f50ba7a0be1a786aeab73"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"predicates-core",
"treeline",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
[[package]]
name = "proc-macro-hack"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.19"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
[[package]]
name = "proc-macro-nested"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.6"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "eba180dafb9038b050a4c280019bbedf9f2467b61e5d892dcad585bb57aadc5a"
Convert WaitUntilZero to std::future::Future
2020-05-08 08:31:33 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "proc-macro2"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.0.24"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "1e0704ee1a7e00d7bb417d0770ea303c1bccbabf0ef1667dae92b5967f5f8a71"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"unicode-xid 0.2.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
Update deps.
2019-12-10 00:17:20 +03:00
name = "publicsuffix"
version = "1.5.4"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "3bbaa49075179162b49acac1c6aa45fb4dafb5f13cf6794276d77bc7fd95757b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"error-chain",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"idna 0.2.0",
"lazy_static",
"regex",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"url 2.2.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
[[package]]
name = "pulldown-cmark"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "8361e81576d2e02643b04950e487ec172b687180da65c731c03cf336784e6c07"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"getopts",
]
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
[[package]]
name = "quick-error"
cargo update
2020-04-28 07:55:50 +03:00
version = "1.2.3"
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
name = "quote"
version = "0.3.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7a6e920b65c65f10b2ae65c831a81a073a89edd28c7cce89475bff467ab4167a"
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "quote"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "1.0.8"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "991431c3519a3f36861882da93630ce66b52918dcf1b8e2fd66b397fc96f28df"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"proc-macro2",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
cargo update
2018-02-01 18:29:23 +03:00
[[package]]
name = "rand"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.4.6"
cargo update
2018-02-01 18:29:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "552840b97013b1a26992c11eac34bdd778e464601a4c2054b5f0bff7c6761293"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"fuchsia-cprng",
"libc",
"rand_core 0.3.1",
"rdrand",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
name = "rand"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.5.6"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "c618c47cd3ebd209790115ab837de41425723956ad3ce2e6a7f09890947cacb9"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"cloudabi",
"fuchsia-cprng",
"libc",
"rand_core 0.3.1",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "rand"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.6.5"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "6d71dacdc3c88c1fde3885a3be3fbab9f35724e6ce99467f7d9c5026132184ca"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"autocfg 0.1.7",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
"rand_chacha 0.1.1",
"rand_core 0.4.2",
"rand_hc 0.1.0",
"rand_isaac",
"rand_jitter",
"rand_os",
"rand_pcg",
"rand_xorshift",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "rand"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.7.3"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"getrandom",
"libc",
cargo update
2020-04-28 07:55:50 +03:00
"rand_chacha 0.2.2",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"rand_core 0.5.1",
"rand_hc 0.2.0",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "rand_chacha"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.1"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "556d3a1ca6600bfcbab7c7c91ccb085ac7fbbcd70e008a98742e7847f4f7bcef"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"autocfg 0.1.7",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"rand_core 0.3.1",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rand_chacha"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.2.2"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"ppv-lite86",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"rand_core 0.5.1",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Switch from SHA-1 to SHA-512 Local benchmarking showed that the implementation of SHA-512 in the *ring* crate is 3x faster than the implementation of SHA-1 in the `sha1` crate. I've also noticed that 80%+ of sccache's runtime on a fully cached build is spent hashing. With this change I noticed a decrease from 108s to 92s when building a fully cached LLVM from the network. Not a huge win but if the network were faster could perhaps add up! Closes #108
2017-04-21 07:09:15 +03:00
[[package]]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
name = "rand_core"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.3.1"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand_core 0.4.2",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "rand_core"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rand_core"
version = "0.5.1"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"getrandom",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "rand_hc"
version = "0.1.0"
Switch from SHA-1 to SHA-512 Local benchmarking showed that the implementation of SHA-512 in the *ring* crate is 3x faster than the implementation of SHA-1 in the `sha1` crate. I've also noticed that 80%+ of sccache's runtime on a fully cached build is spent hashing. With this change I noticed a decrease from 108s to 92s when building a fully cached LLVM from the network. Not a huge win but if the network were faster could perhaps add up! Closes #108
2017-04-21 07:09:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7b40677c7be09ae76218dc623efbf7b18e34bced3f38883af07bb75630a21bc4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand_core 0.3.1",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand_core 0.5.1",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "rand_isaac"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ded997c9d5f13925be2a6fd7e66bf1872597f759fd9dd93513dd7e92e5a5ee08"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand_core 0.3.1",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rand_jitter"
version = "0.1.4"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "1166d5c91dc97b88d1decc3285bb0a99ed84b05cfd0bc2341bdf2d43fc41e39b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
"rand_core 0.4.2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rand_os"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7b75f676a1e053fc562eafbb47838d67c84801e38fc1ba459e8f180deabd5071"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"cloudabi",
"fuchsia-cprng",
"libc",
"rand_core 0.4.2",
"rdrand",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "rand_pcg"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.2"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "abf9b09b01790cfe0364f52bf32995ea3c39f4d2dd011eac241d2914146d0b44"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"autocfg 0.1.7",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"rand_core 0.4.2",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
Roll back some minor version upgrades. Fixes #593 Unfortunately these cause some issues not covered by CI.
2019-11-12 20:30:01 +03:00
name = "rand_xorshift"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.1"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "cbf7e9e623549b0e21f6e97cf8ecf247c1a8fd2e8a992ae265314300b2455d5c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand_core 0.3.1",
]
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rdrand"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand_core 0.3.1",
]
Switch from SHA-1 to SHA-512 Local benchmarking showed that the implementation of SHA-512 in the *ring* crate is 3x faster than the implementation of SHA-1 in the `sha1` crate. I've also noticed that 80%+ of sccache's runtime on a fully cached build is spent hashing. With this change I noticed a decrease from 108s to 92s when building a fully cached LLVM from the network. Not a huge win but if the network were faster could perhaps add up! Closes #108
2017-04-21 07:09:15 +03:00
Add a Redis cache variant This cache module uses a Redis instance. To make sccache use this, set SCCACHE_REDIS to redis://[:<passwd>@]<hostname>[:port][/<db>]. The maximum and current cache size is retrieved from the INFO and CONFIG GET redis command.
2017-02-16 22:56:41 +03:00
[[package]]
name = "redis"
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
version = "0.17.0"
Add a Redis cache variant This cache module uses a Redis instance. To make sccache use this, set SCCACHE_REDIS to redis://[:<passwd>@]<hostname>[:port][/<db>]. The maximum and current cache size is retrieved from the INFO and CONFIG GET redis command.
2017-02-16 22:56:41 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
checksum = "95357caf2640abc54651b93c98a8df4fe1ccbf44b8e601ccdf43d5c1451f29ac"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"async-std",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"async-trait",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"bytes 0.5.6",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"combine",
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
"dtoa",
"futures-util",
"itoa",
"percent-encoding 2.1.0",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"pin-project-lite 0.1.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"sha1",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"tokio 0.2.24",
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
"tokio-util",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"url 2.2.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Add a Redis cache variant This cache module uses a Redis instance. To make sccache use this, set SCCACHE_REDIS to redis://[:<passwd>@]<hostname>[:port][/<db>]. The maximum and current cache size is retrieved from the INFO and CONFIG GET redis command.
2017-02-16 22:56:41 +03:00
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
[[package]]
name = "redox_syscall"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.57"
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
Update deps.
2019-12-10 00:17:20 +03:00
name = "redox_users"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.3.5"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "de0737333e7a9502c789a36d7c7fa6092a49895d4faa31ca5df163857ded2e9d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"getrandom",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"redox_syscall",
"rust-argon2",
]
Update ring
2018-01-07 18:33:04 +03:00
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
[[package]]
name = "regex"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.4.2"
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "38cf2c13ed4745de91a5eb834e11c00bcc3709e773173b2ce4c56c9fbde04b9c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"aho-corasick",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"memchr",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"regex-syntax",
"thread_local",
]
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
[[package]]
name = "regex-syntax"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.6.21"
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "3b181ba2dcf07aaccad5448e8ead58db5b742cf85dfe035e2227f137a539a189"
Switch from assert_cli to assert_cmd
2018-07-26 22:52:50 +03:00
cargo update
2018-02-01 18:29:23 +03:00
[[package]]
name = "remove_dir_all"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.3"
cargo update
2018-02-01 18:29:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update ring
2018-01-07 18:33:04 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "reqwest"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.9.24"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "f88643aea3c1343c804950d7bf983bd2067f5ab59db6d613a08e05572f2714ab"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"base64 0.10.1",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"cookie",
"cookie_store",
"encoding_rs",
"flate2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"http",
"hyper",
"hyper-tls",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
cargo update
2020-04-28 07:55:50 +03:00
"mime 0.3.16",
"mime_guess 2.0.3",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"native-tls",
"serde",
"serde_json",
"serde_urlencoded",
"time",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"tokio 0.1.22",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-executor",
"tokio-io",
"tokio-threadpool",
"tokio-timer",
"url 1.7.2",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"uuid 0.7.4",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"winreg",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "retry"
Upgrade retry to 1.2
2020-12-10 02:11:07 +03:00
version = "1.2.0"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade retry to 1.2
2020-12-10 02:11:07 +03:00
checksum = "c15ef4789108d066d7fd85dcec330eab9b8e51244275922a9b7161afc4f46dda"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade retry to 1.2
2020-12-10 02:11:07 +03:00
"rand 0.7.3",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Switch from SHA-1 to SHA-512 Local benchmarking showed that the implementation of SHA-512 in the *ring* crate is 3x faster than the implementation of SHA-1 in the `sha1` crate. I've also noticed that 80%+ of sccache's runtime on a fully cached build is spent hashing. With this change I noticed a decrease from 108s to 92s when building a fully cached LLVM from the network. Not a huge win but if the network were faster could perhaps add up! Closes #108
2017-04-21 07:09:15 +03:00
[[package]]
name = "ring"
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
version = "0.16.19"
Switch from SHA-1 to SHA-512 Local benchmarking showed that the implementation of SHA-512 in the *ring* crate is 3x faster than the implementation of SHA-1 in the `sha1` crate. I've also noticed that 80%+ of sccache's runtime on a fully cached build is spent hashing. With this change I noticed a decrease from 108s to 92s when building a fully cached LLVM from the network. Not a huge win but if the network were faster could perhaps add up! Closes #108
2017-04-21 07:09:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
checksum = "024a1e66fea74c66c66624ee5622a7ff0e4b73a13b4f5c326ddb50c708944226"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"cc",
"libc",
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"once_cell",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"spin",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"untrusted",
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"web-sys",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update ring
2018-01-07 18:33:04 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "rouille"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
version = "3.0.0"
Fixes for updated deps, bump rouille, better logging
2018-09-04 22:36:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
checksum = "112568052ec17fa26c6c11c40acbb30d3ad244bf3d6da0be181f5e7e42e5004f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"base64 0.9.3",
"chrono",
update filetime for lru-disk-cache: 0.1 -> 0.2
2020-07-14 13:28:11 +03:00
"filetime",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"multipart",
"num_cpus",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"rand 0.5.6",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"serde",
"serde_derive",
"serde_json",
"sha1",
"term",
"threadpool",
"time",
Revert "Bump to tiny-http 0.7.0 (#830)" because it caused a regression, #846. This reverts commit bdaa65aead6053ff707b1c20320e213d29d4bb55.
2020-09-17 03:51:29 +03:00
"tiny_http",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"url 1.7.2",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "rust-argon2"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.8.3"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "4b18820d944b33caa75a71378964ac46f58517c92b6ae5f762636247c09e78fb"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"base64 0.13.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"blake2b_simd",
cargo update
2020-04-28 07:55:50 +03:00
"constant_time_eq",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"crossbeam-utils 0.8.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update deps.
2019-12-10 00:17:20 +03:00
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
[[package]]
name = "rustc-demangle"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.18"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "6e3bad0ee36814ca07d7968269dd4b7ec89ec2da10c4bb613928d3077083c232"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"semver",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "ryu"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "1.0.5"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "safemem"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.3.3"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ef703b7cb59335eae2eb93ceb664c0eb7ea6bf567079d843e09420219668e072"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
Rebuild Cargo.lock with cargo 0.23
2017-12-05 16:32:33 +03:00
[[package]]
name = "sccache"
(cargo-release) start next development iteration 0.2.16-alpha.0
2021-01-13 01:26:44 +03:00
version = "0.2.16-alpha.0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Change error handling from `error-chain` to `anyhow`. Because `anyhow` is what seems to be the most common error library for applications these days. - The global `Result` type is now `anyhow::Result`. - In errors.rs, there's no need for any boilerplate to wrap all the foreign errors seen: `hyper::Error`, `io:Error`, etc. - The internal errors that we care about are now separate types, rather than within an enum, because that works better when we need to check for them by downcasting an `anyhow::Error`. And it's nice to write `Err(ProcessError(output))` rather than `Err(ErrorKind::ProcessError(output))`. - The `Which` error was unused and is removed. - The most common change is that `.chain_err()` is changed to `.context`/`.with_context()`. - `anyhow!` is used where necessary, mostly to promote a string to an `anyhow::Error`. - Errors within futures: `FutureChainErr`/`.chain_err()` is changed to `FutureContext`/`fcontext`/`fwith_context`. The `f` prefix is because I found it helpful to distinguish these cases from the simple error cases. - `BuilderIncoming`, `SchedulerIncoming`, `ServerIncoming` no longer have an `Error` associated type, we just use `anyhow::Error` uniformly. - `e.display_chain()` changes to `format!("{:?}")`, because they both print the full cause chain, and the backtrace (if present). - A few places where the old code was doing something weird or more complicated than seemed necessary, I generally tried to replace it with something simpler and more typical. Two places used `with_boxed_chain()`, which doesn't have an equivalent in `anyhow`, so I did my best to do something reasonable. - In `src/server.rs` we now import `std::task::Context` as `TaskContext` to avoid overshadowing the `anyhow::Context` trait :(
2020-06-02 10:22:31 +03:00
"anyhow",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"ar",
"assert_cmd",
"atty",
Upgrade base64 to 0.13
2020-12-10 02:00:26 +03:00
"base64 0.13.0",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"bincode 1.3.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"blake3",
"byteorder",
"cc",
"chrono",
"clap",
"counted-array",
Upgrade crossbeam
2020-10-07 05:42:26 +03:00
"crossbeam-utils 0.8.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"daemonize",
"directories",
"env_logger",
update filetime for lru-disk-cache: 0.1 -> 0.2
2020-07-14 13:28:11 +03:00
"filetime",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"flate2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"futures 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"hmac",
"http",
"hyper",
"hyperx",
Upgrade itertools to 0.10
2021-01-08 10:28:43 +03:00
"itertools 0.10.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"jobserver",
"jsonwebtoken",
"lazy_static",
"libc",
"libmount",
Move lru-disk-cache to an internal module See discussion in #916
2021-01-07 08:08:48 +03:00
"linked-hash-map",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"local-encoding",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"md-5",
"memcached-rs",
Upgrade nix to 0.19
2020-12-10 01:56:41 +03:00
"nix 0.19.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"num_cpus",
"number_prefix",
"openssl",
Upgrade url to 2.2
2020-12-10 01:19:22 +03:00
"percent-encoding 2.1.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"predicates",
Upgrade to rand 0.7
2020-12-09 12:03:48 +03:00
"rand 0.7.3",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"redis",
"regex",
"reqwest",
"retry",
"ring",
"rouille",
"selenium-rs",
"serde",
"serde_derive",
"serde_json",
"sha-1",
"sha2",
"strip-ansi-escapes",
"syslog",
"tar",
"tempfile",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"tokio-compat",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-io",
"tokio-named-pipes",
"tokio-process",
"tokio-reactor",
"tokio-serde-bincode",
"tokio-tcp",
"tokio-timer",
"tokio-uds",
"toml",
"tower",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"untrusted",
Upgrade url to 2.2
2020-12-10 01:19:22 +03:00
"url 2.2.0",
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"uuid 0.8.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"version-compare",
"void",
update walkdir 1 -> 2.3
2020-07-14 13:14:02 +03:00
"walkdir",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"which",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"zip",
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
"zstd",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rebuild Cargo.lock with cargo 0.23
2017-12-05 16:32:33 +03:00
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
[[package]]
name = "schannel"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.1.19"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "8f05ba609c234e60bee0d547fe94a4c7e9da733d1c962cf6e59efa4cd9c8bc75"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"lazy_static",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
[[package]]
name = "scopeguard"
cargo update
2020-04-28 07:55:50 +03:00
version = "1.1.0"
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
Update dependencies Notably bring in hyper from crates.io
2017-06-14 18:20:12 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "security-framework"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "2.0.0"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "c1759c2e3c8580017a484a7ac56d3abc5a6c1feadf88db2f3633f12ae4268c69"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"bitflags",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"core-foundation",
"core-foundation-sys",
"libc",
"security-framework-sys",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "security-framework-sys"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "2.0.0"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "f99b9d5e26d2a71633cc4f2ebae7cc9f874044e0c351a27e17892d76dce5678b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"core-foundation-sys",
cargo update
2020-04-28 07:55:50 +03:00
"libc",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Selenium tests for oauth
2018-10-23 10:33:42 +03:00
[[package]]
name = "selenium-rs"
use a proper release for selenium-rs 0.1.2 was released earlier this year and includes the fix we need.
2020-06-12 20:54:45 +03:00
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "01173ad274e14fafa534a5e660d950ca1939ccebd3955df987b7df7e4e301108"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"reqwest",
"serde",
"serde_derive",
"serde_json",
"url 1.7.2",
]
Selenium tests for oauth
2018-10-23 10:33:42 +03:00
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
[[package]]
name = "semver"
chore: Update memcached to 0.3
2018-08-28 15:42:57 +03:00
version = "0.9.0"
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"semver-parser",
]
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
chore: Update memcached to 0.3
2018-08-28 15:42:57 +03:00
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
chore: Update memcached to 0.3
2018-08-28 15:42:57 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "serde"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.0.118"
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "06c64263859d87aa2eb554587e2d23183398d617427327cf2b3d0ed8c69e4800"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"serde_derive",
]
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
name = "serde_derive"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.0.118"
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "c84d3526699cd55261af4b941e4e725444df67aa4f9e6a3564f18030d12672df"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "serde_json"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.61"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "4fceb2595057b6891a4ee808f70054bd2d12f0e97f1cbb78689b59f676df325a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"itoa",
"ryu",
"serde",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "serde_urlencoded"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.5.5"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "642dd69105886af2efd227f75a520ec9b44a820d65bc133a9131f7d229fd165a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"dtoa",
"itoa",
"serde",
"url 1.7.2",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "sha-1"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.9.2"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "ce3cdf1b5e620a498ee6f2a171885ac7e22f0e12089ec4b3d22b84921792507c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"block-buffer",
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"cfg-if 1.0.0",
"cpuid-bool",
"digest",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"opaque-debug",
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
[[package]]
name = "sha1"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "2579985fda508104f7587689507983eadd6a6e84dd35d6d115361f530916fa0d"
Add overlay builder (with bubblewrap), serde tweaks
2018-07-15 16:37:46 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "sha2"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
version = "0.9.2"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
checksum = "6e7aab86fe2149bad8c507606bdb3f4ef5e7b2380eb92350f56122cca72a42a8"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"block-buffer",
Upgrade hmac to 0.10 and md-5, sha-1 and sha2 to 0.9
2020-12-10 01:39:52 +03:00
"cfg-if 1.0.0",
"cpuid-bool",
"digest",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"opaque-debug",
]
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "signal-hook-registry"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "1.3.0"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "16f1d0fef1604ba8f7a073c7e701f213e056707210e9020af4528e0101ce11a6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "simple_asn1"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "692ca13de57ce0613a363c8c2f1de925adebc81b04c923ac60c5488bb44abe4b"
dependencies = [
"chrono",
"num-bigint",
"num-traits 0.2.14",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "siphasher"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "0b8de496cf83d4ed58b6be86c3a275b8602f6ffe98d3024a869e124147a9a3ac"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
[[package]]
name = "skeptic"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "24ebf8a06f5f8bae61ae5bbc7af7aac4ef6907ae975130faba1199e5fe82256a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"pulldown-cmark",
"tempdir",
]
use local-encoding crate for stdout conversion
2016-09-21 22:57:28 +03:00
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
[[package]]
name = "slab"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "c111b5bd5695e56cffe5129854aa230b39c93a305372fdbb2668ca2394eea9f8"
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "smallvec"
Update the minimum set of deps for cargo audit cargo audit now reports 0 vulnerabilities down from 3
2021-05-12 02:08:35 +03:00
version = "0.6.14"
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update the minimum set of deps for cargo audit cargo audit now reports 0 vulnerabilities down from 3
2021-05-12 02:08:35 +03:00
checksum = "b97fcaeba89edba30f044a10c6a3cc39df9c3f17d7cd829dd1446cab35f890e0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"maybe-uninit",
]
Update iovec to fix a soundness hole on Windows Also update a few other dependencies that transitively needed fixing
2017-10-06 02:40:25 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "socket2"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "0.3.19"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "122e570113d28d773067fab24266b66753f6ea915758651696b6e35e49f88d6e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 1.0.0",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update ring
2018-01-07 18:33:04 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
name = "spin"
version = "0.5.2"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "6e63cff320ae2c57904679ba7cb63280a3dc4613885beafb148ee7bf9aa9042d"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "string"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.2.1"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "d24114bfcceb867ca7f71a0d3fe45d45619ec47a6fbfa98cb14e14250bfa5d6d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
[[package]]
name = "strip-ansi-escapes"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "9d63676e2abafa709460982ddc02a3bb586b6d15a49b75c212e06edd3933acee"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"vte",
]
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "strsim"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.8.0"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "subtle"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "2.4.0"
Run `cargo update`
2020-12-08 08:07:09 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "1e81da0851ada1f3e9d4312c704aa4f8806f0f9d69faaf8df2f3464b4a9437c2"
Run `cargo update`
2020-12-08 08:07:09 +03:00
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
name = "syn"
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
version = "0.11.11"
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "d3b891b9015c88c576343b9b3e41c2c11a51c219ef067b264bd9c8aa9b441dad"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"quote 0.3.15",
"synom",
"unicode-xid 0.0.4",
]
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
Roll back some minor version upgrades. Fixes #593 Unfortunately these cause some issues not covered by CI.
2019-11-12 20:30:01 +03:00
[[package]]
name = "syn"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.58"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "cc60a3d73ea6594cd712d830cc1f0390fd71542d8c8cd24e70cc54cdfd5e05d5"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"unicode-xid 0.2.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
name = "synom"
version = "0.11.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "a393066ed9010ebaed60b9eafa373d4b1baac186dd7e008555b0f702b51945b6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"unicode-xid 0.0.4",
]
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
[[package]]
name = "synstructure"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.12.4"
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "b834f2d66f734cb897113e34aaff2f1ab4719ca946f9a7358dba8f8064148701"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"unicode-xid 0.2.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
chore: Update which to 2 The error type no longer implements ::std::error::Error (it implements failure::Fail instead) so I had to add a wrapper for it.
2018-08-28 15:57:35 +03:00
Add syslog logging for sccache-dist. Fixes #380 This change adds a `--syslog=level` argument to the sccache-dist `scheduler` and `server` commands that sends logs to syslog.
2019-02-28 22:42:56 +03:00
[[package]]
name = "syslog"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
version = "5.0.0"
Add syslog logging for sccache-dist. Fixes #380 This change adds a `--syslog=level` argument to the sccache-dist `scheduler` and `server` commands that sends logs to syslog.
2019-02-28 22:42:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
checksum = "9a5d8ef1b679c07976f3ee336a436453760c470f54b5e7237556728b8589515d"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"error-chain",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"time",
]
Add syslog logging for sccache-dist. Fixes #380 This change adds a `--syslog=level` argument to the sccache-dist `scheduler` and `server` commands that sends logs to syslog.
2019-02-28 22:42:56 +03:00
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
[[package]]
name = "tar"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.4.30"
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "489997b7557e9a43e192c527face4feacc78bfbe6eed67fd55c4c9e381cba290"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
update filetime for lru-disk-cache: 0.1 -> 0.2
2020-07-14 13:28:11 +03:00
"filetime",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
"redox_syscall",
"xattr",
]
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "tempdir"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
version = "0.3.7"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "15f2b5fb00ccdf689e0149d1b1b3c03fead81c2b37735d812fa8bddbbf41b6d8"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand 0.4.6",
"remove_dir_all",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Atomically create compiler outputs from cache entries. Fixes #122. I was seeing intermittent rustc panics when compiling with sccache. It turns out that rustc will wind up looking for rlibs in the output dir and sometimes it finds the ones that we're in the middle of writing out from cache and it panics trying to read the half-written file. This change makes us write the cache entry to a tempfile and atomically rename it to the final name.
2017-05-17 23:38:12 +03:00
[[package]]
name = "tempfile"
Update deps.
2019-12-10 00:17:20 +03:00
version = "3.1.0"
Atomically create compiler outputs from cache entries. Fixes #122. I was seeing intermittent rustc panics when compiling with sccache. It turns out that rustc will wind up looking for rlibs in the output dir and sometimes it finds the ones that we're in the middle of writing out from cache and it panics trying to read the half-written file. This change makes us write the cache entry to a tempfile and atomically rename it to the final name.
2017-05-17 23:38:12 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
cargo update
2020-04-28 07:55:50 +03:00
"rand 0.7.3",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"redox_syscall",
"remove_dir_all",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Atomically create compiler outputs from cache entries. Fixes #122. I was seeing intermittent rustc panics when compiling with sccache. It turns out that rustc will wind up looking for rlibs in the output dir and sometimes it finds the ones that we're in the middle of writing out from cache and it panics trying to read the half-written file. This change makes us write the cache entry to a tempfile and atomically rename it to the final name.
2017-05-17 23:38:12 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "term"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.5.2"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "edd106a334b7657c10b7c540a0106114feadeb4dc314513e97df481d5d966f42"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"byteorder",
"dirs",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
[[package]]
name = "termcolor"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "1.1.2"
Roll back some minor version upgrades. Fixes #593 Unfortunately these cause some issues not covered by CI.
2019-11-12 20:30:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "2dfed899f0eb03f32ee8c6a0aabdb8a7949659e3466561fc0adf54e26d88c5f4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"winapi-util",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
Update ring
2018-01-07 18:33:04 +03:00
name = "textwrap"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.11.0"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"unicode-width",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
[[package]]
name = "thiserror"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.23"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "76cc616c6abf8c8928e2fdcc0dbfab37175edd8fb49a4641066ad1364fdab146"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.0.23"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "9be73a2caec27583d0046ef3796c3794f868a5bc813db689eed00c7631275cd1"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "thread_local"
Run `cargo update`
2021-01-08 10:26:06 +03:00
version = "1.1.0"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2021-01-08 10:26:06 +03:00
checksum = "bb9bc092d0d51e76b2b19d9d85534ffc9ec2db959a2523cdae0697e2972cd447"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"lazy_static",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "threadpool"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "1.8.1"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "d050e60b33d41c19108b32cea32164033a9013fe3b46cbd4457559bfbf77afaa"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"num_cpus",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "time"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.44"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"wasi 0.10.0+wasi-snapshot-preview1",
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "tiny_http"
Update the minimum set of deps for cargo audit cargo audit now reports 0 vulnerabilities down from 3
2021-05-12 02:08:35 +03:00
version = "0.6.4"
Workaround tiny_http issue #151 by disabling HTTP pipelining Instead of relying on a crate patch.
2021-01-08 08:27:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update the minimum set of deps for cargo audit cargo audit now reports 0 vulnerabilities down from 3
2021-05-12 02:08:35 +03:00
checksum = "2e22cb179b63e5fc2d0b5be237dc107da072e2407809ac70a8ce85b93fe8f562"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"ascii",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"chrono",
Revert "Bump to tiny-http 0.7.0 (#830)" because it caused a regression, #846. This reverts commit bdaa65aead6053ff707b1c20320e213d29d4bb55.
2020-09-17 03:51:29 +03:00
"chunked_transfer",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"openssl",
"url 1.7.2",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "tinyvec"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ccf8dbc19eb42fba10e8feaaec282fb50e2c14b2726d6301dbfeed0f73306a6f"
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cda74da7e1a664f795bb1f8a87ec406fb89a02522cf6e50620d016add6dbbf5c"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.1.22"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "5a09c0b5bb588872ab2f09afa13ee6e9dac11e10a0ec9e8e3ba39a5a5d530af6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"num_cpus",
"tokio-codec",
"tokio-current-thread",
"tokio-executor",
"tokio-fs",
"tokio-io",
"tokio-reactor",
"tokio-sync",
"tokio-tcp",
"tokio-threadpool",
"tokio-timer",
"tokio-udp",
"tokio-uds",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "tokio"
Run `cargo update`
2020-12-10 03:19:32 +03:00
version = "0.2.24"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-10 03:19:32 +03:00
checksum = "099837d3464c16a808060bb3f02263b412f6fafcb5d01c533d309985fbeebe48"
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"bytes 0.5.6",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"fnv",
"futures-core",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"iovec",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"lazy_static",
Upgrade redis to 0.18
2020-12-10 01:47:15 +03:00
"libc",
"memchr",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
"mio-uds",
"num_cpus",
"pin-project-lite 0.1.11",
Upgrade redis to 0.18
2020-12-10 01:47:15 +03:00
"slab",
]
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
[[package]]
name = "tokio-buf"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "8fb220f46c53859a4b7ec083e41dec9778ff0b1851c0942b211edb89e0ccdc46"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"either",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-codec"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.2"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "25b2998660ba0e70d18684de5d06b70b70a3a747469af9dea7618cc59e75976b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-io",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
[[package]]
name = "tokio-compat"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "107b625135aa7b9297dd2d99ccd6ca6ab124a5d1230778e159b9095adca4c722"
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"futures-core",
"futures-util",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"pin-project-lite 0.1.11",
Run `cargo update`
2020-12-10 03:19:32 +03:00
"tokio 0.2.24",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"tokio-current-thread",
"tokio-executor",
"tokio-reactor",
"tokio-timer",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "tokio-current-thread"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.7"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "b1de0e32a83f131e002238d7ccde18211c0a5397f60cbfffcb112868c2e0e20e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-executor",
]
Update to using the new tokio-io crate This is an abstraction of the Tokio stack now and doesn't have much impact on sccache itself but I figured it'd be good to update a few deps and pick up the recent version of things! Plus that and I'd like to start using the length_delimited module soon...
2017-03-09 21:00:18 +03:00
[[package]]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
name = "tokio-executor"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.10"
Update to using the new tokio-io crate This is an abstraction of the Tokio stack now and doesn't have much impact on sccache itself but I figured it'd be good to update a few deps and pick up the recent version of things! Plus that and I'd like to start using the length_delimited module soon...
2017-03-09 21:00:18 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "fb2d1b8f4548dbf5e1f7818512e9c406860678f29c300cdf0ebac72d1a3a1671"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-fs"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.7"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "297a1206e0ca6302a0eed35b700d292b275256f596e2f3fea7729d5e629b6ff4"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-io",
"tokio-threadpool",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-io"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.13"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "57fc868aae093479e3131e3d165c93b1c7474109d13c90ec0dda2a1bbfff0674"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
[[package]]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
name = "tokio-named-pipes"
version = "0.1.0"
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "9d282d483052288b2308ba5ee795f5673b159c9bdf63c385a05609da782a5eae"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"mio-named-pipes",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"tokio 0.1.22",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
[[package]]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
name = "tokio-process"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.2.5"
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "382d90f43fa31caebe5d3bc6cfd854963394fff3b8cb59d5146607aaae7e7e43"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-queue 0.1.2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"lazy_static",
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"mio-named-pipes",
"tokio-io",
"tokio-reactor",
"tokio-signal",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rewrite the server module with Tokio This commit rewrites the `server` module of sccache to be backed with Tokio. The previous version was written with `mio`, which Tokio is built on, but is unfortunately less ergonomic. Tokio is the state-of-the-art for asynchronous programming in Rust and sccache serves as a great testing ground for ergonomics! It's intended that the support added here will eventually extend to many other operations that sccache does as well. For example thread spawning has all been replaced with `CpuPool` to have a shared pool for I/O operations and such (namely the filesystem). Eventually the HTTP requests made by the S3 backend can be integrated with the Tokio branch of Hyper as well to run that on the event loop instead of in a worker thread. I'd also like to eventually extend this with `tokio-process` as well to move process spawning off helper threads as well, but I'm leaving that to a future commit as well. Overall I found the transition was quite smooth, with the high level architecture look like: * The `tokio-proto` crate is used in streaming mode. The streaming part is used for the one RPC sccache gets which requires a second response to be sent later on. This second response is the "response body" in tokio-proto terms. * All of sccache's logic is manifested in an implementation of the `Service` trait. * The transport layer is provided with `tokio_core::io::{Framed, Codec}`, and simple deserialization/serialization is performed with protobuf. Some differences in design are: * The `SccacheService` for now is just a bunch of reference-counted pointers, making it cheap to clone. As the futures it returns progress they will each retain a reference to a cloned copy of the `SccacheService`. Before all this data was just stored and manipulated in a struct directly, but it's now directly managed through shared memory. * The storage backends share a thread pool with the main server instead of spawning threads. And finally, some things I've learned along the way: * Sharing data between futures isn't a trivial operation. It took an explicit decision to use `Rc` and I'm not sure I'm 100% happy with how the ergonomics played out. * Shutdown is pretty tricky here. I've tried to carry over all the previous logic but it definitely required not using `TcpServer` in tokio-proto at the very least, and otherwise required a few custom futures and such to track the various states. I have a hunch that tokio-proto could provide more options out of the box for something like this.
2017-01-31 04:04:03 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-reactor"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.12"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "09bc590ec4ba8ba87652da2068d150dcada2cfa2e07faae270a5e0409aa51351"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"lazy_static",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"num_cpus",
"parking_lot",
"slab",
"tokio-executor",
"tokio-io",
"tokio-sync",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
name = "tokio-serde"
version = "0.1.0"
Depend on tokio-serde-bincode from crates.io
2017-07-13 21:33:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "894168193c4f80862a2244ff953b69145a9961a9efba39500e0970b083d0649c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
name = "tokio-serde-bincode"
Depend on tokio-serde-bincode from crates.io
2017-07-13 21:33:57 +03:00
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "02e35c8d60a5e87cfb30dd562a309e56f8a6d36617b0a76c87f04d5466607ca8"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"bincode 0.8.0",
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"derive-error",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"serde",
"tokio-serde",
]
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
[[package]]
name = "tokio-signal"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.2.9"
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "d0c34c6e548f101053321cba3da7cbb87a610b85555884c41b07da2eb91aff12"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"mio-uds",
cargo update
2020-04-28 07:55:50 +03:00
"signal-hook-registry",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-executor",
"tokio-io",
"tokio-reactor",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Integrate process spawning with tokio-process This commit replaces all process spawning with the futures-powered versions in the `tokio-process` crate. Most functions were already ready to return futures, but a few minor updates were made to ensure that functions could return futures. Additionally, some `&CpuPool` arguments have shown up to allow executing work on a thread pool, such as filesystem operations. A number of compilers write data to tempdirs and such before running a compiler, and these are all executed on thread pools rather than the main thread. My main takeaway from this commit is that translating synchronous to asynchronous code isn't always easy. The "easy" version ends up being relatively wasteful in terms of clones for low-level performance, but probably shouldn't matter much in the context of spawning processes. Other than that though I found that there was a translation for all patterns found didn't actually hit any bugs (yet at least) from the translation.
2017-02-01 03:19:35 +03:00
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
[[package]]
name = "tokio-sync"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.8"
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "edfe50152bc8164fcc456dab7891fa9bf8beaf01c5ee7e1dd43a397c3cf87dee"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"fnv",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-tcp"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.4"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "98df18ed66e3b72e742f185882a9e201892407957e45fbff8da17ae7a7c51f72"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"iovec",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-io",
"tokio-reactor",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-threadpool"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.18"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "df720b6581784c118f0eb4310796b12b1d242a7eb95f716a8367855325c25f89"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"crossbeam-deque",
`cargo update`
2020-06-11 04:40:05 +03:00
"crossbeam-queue 0.2.3",
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"lazy_static",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"num_cpus",
"slab",
"tokio-executor",
]
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-timer"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.2.13"
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "93044f2d313c95ff1cb7809ce9a7a05735b012288a888b62d4434fd58c94f296"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
cargo update
2020-04-28 07:55:50 +03:00
"crossbeam-utils 0.7.2",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"slab",
"tokio-executor",
]
Roll back some minor version upgrades. Fixes #593 Unfortunately these cause some issues not covered by CI.
2019-11-12 20:30:01 +03:00
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
[[package]]
name = "tokio-udp"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.6"
Use redis-0.9 for async requests
2018-08-27 17:23:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "e2a0b10e610b39c38b031a2fcab08e4b82f16ece36504988dcbd81dbba650d82"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
"log 0.4.11",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-codec",
"tokio-io",
"tokio-reactor",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "tokio-uds"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.7"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "ab57a4ac4111c8c9dbcf70779f6fc8bc35ae4b2454809febac840ad19bd7e4e0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Use tokio-compat instead of tokio This gets us one step into tokio 0.2, with its new scheduler. This makes things significantly faster on my 32-core 64-threads machine, with Firefox builds with 100% cache hits at -j64 going down from 3 minutes to 2:24. Also, with the old scheduler, with 100% cache hits, -j16 was actually faster than -j64, which is not the case anymore.
2020-04-28 08:28:17 +03:00
"bytes 0.4.12",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"iovec",
"libc",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"mio",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"mio-uds",
"tokio-codec",
"tokio-io",
"tokio-reactor",
]
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
[[package]]
name = "tokio-util"
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
version = "0.3.1"
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
checksum = "be8242891f2b6cbef26a2d7e8605133c2c554cd35b3e4948ea892d6d68436499"
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"bytes 0.5.6",
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
"futures-core",
"futures-sink",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"log 0.4.11",
"pin-project-lite 0.1.11",
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
"tokio 0.2.24",
feat: Update redis to 0.15 With tokio-compat being used it is now possible to use dependencies that use tokio-0.2
2020-04-29 11:59:38 +03:00
]
Allow configuration of caches with a config file
2018-06-04 20:28:39 +03:00
[[package]]
name = "toml"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "0.5.8"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "a31142970826733df8241ef35dc040ef98c679ab14d7c3e54d827099b3acecaa"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"serde",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "dc72f33b6a72c75c9df0037afce313018bae845f0ec7fdb9201b8768427a917f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tower-buffer",
"tower-discover",
"tower-layer",
"tower-limit",
"tower-load-shed",
"tower-retry",
"tower-service",
"tower-timeout",
"tower-util",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-buffer"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "3c7b83e1ccf5b23dd109dd6ae2c07b8e2beec7a51a21f29da2dba576317370e0"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-executor",
"tokio-sync",
"tower-layer",
"tower-service",
"tracing",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-discover"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "73a7632286f78164d65d18fd0e570307acde9362489aa5c8c53e6315cc2bde47"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tower-service",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-layer"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "0ddf07e10c07dcc8f41da6de036dc66def1a85b70eb8a385159e3908bb258328"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tower-service",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-limit"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
version = "0.1.3"
Allow configuration of caches with a config file
2018-06-04 20:28:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
checksum = "c21ba835a08fd54b63cd91ae0548a7b6e2a91075147dfa3dc8e1a940c1b6f18f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-sync",
"tokio-timer",
"tower-layer",
"tower-service",
"tracing",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-load-shed"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "04fbaf5bfb63d84204db87b9b2aeec61549613f2bbb8706dcc36f5f3ea8cd769"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tower-layer",
"tower-service",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-retry"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "09e80588125061f276ed2a7b0939988b411e570a2dbb2965b1382ef4f71036f7"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-timer",
"tower-layer",
"tower-service",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-service"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "2cc0c98637d23732f8de6dfd16494c9f1559c3b9e20b4a46462c8f9b9e827bfa"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-timeout"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "5c06bbc2fbd056f810940a8c6f0cc194557d36da3c22999a755a7a6612447da9"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-timer",
"tower-layer",
"tower-service",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tower-util"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "4792342fac093db5d2558655055a89a04ca909663467a4310c7739d9f8b64698"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tokio-io",
"tower-layer",
"tower-service",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tracing"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.22"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "9f47026cdc4080c07e49b37087de021820269d996f581aac150ef9e5583eefe3"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 1.0.0",
"log 0.4.11",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"pin-project-lite 0.2.1",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"tracing-attributes",
"tracing-core",
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tracing-attributes"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.11"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "80e0ccfc3378da0cce270c946b676a376943f5cd16aeba64568e7939806f4ada"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
`cargo update`
2020-06-11 04:40:05 +03:00
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
[[package]]
name = "tracing-core"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.17"
Replace deprecated `tokio-service` with `tower`.
2019-11-11 00:25:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "f50de3927f93d202783f4513cda820ab47ef17f624b03c096e86ef00c67e6b5f"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"lazy_static",
]
Allow configuration of caches with a config file
2018-06-04 20:28:39 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "treeline"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "a7f741b240f1a48843f9b8e0444fb55fb2a4ff67293b50a9179dfd5ea67f8d41"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "try-lock"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.3"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "59547bce71d9c38b83d9c0e92b6066c4253371f15005def0c30d9657f50c7642"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "try_from"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "283d3b89e1368717881a9d51dad843cc435380d8109c9e47d38780a324698d8b"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update deps.
2019-12-10 00:17:20 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "twoway"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "59b11b2b5241ba34be09c3cc85a36e56e48f9888862e19cedf23336d35316ed1"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
"memchr",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
[[package]]
name = "typenum"
cargo update
2020-04-28 07:55:50 +03:00
version = "1.12.0"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "373c8a200f9e67a0c95e62a4f52fbf80c23b4381c05a17845531982fa99e6b33"
Replace rust-crypto with RustCrypto/hashes
2019-10-25 02:43:35 +03:00
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "unicase"
version = "1.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "7f4765f83163b74f957c797ad9253caf97f103fb064d3999aea9568d09fc8a33"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"version_check 0.1.5",
]
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "unicase"
Update deps.
2019-12-10 00:17:20 +03:00
version = "2.6.0"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "50f37be617794602aabbeee0be4f259dc1778fabe05e2d67ee8f79326d5cb4f6"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
`cargo update`
2020-06-11 04:40:05 +03:00
"version_check 0.9.2",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "unicode-bidi"
Update ring
2018-01-07 18:33:04 +03:00
version = "0.3.4"
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "49f2bd0c6468a8230e1db229cff8029217cf623c767ea5d60bfbd42729ea54d5"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"matches",
]
Implement S3Cache Unlike sccache1, you need to specify both bucket and region, like: SCCACHE_BUCKET=sccache SCCACHE_REGION=us-east-1 Pretty limited testing, no automated tests currently.
2016-06-03 22:09:38 +03:00
[[package]]
name = "unicode-normalization"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.16"
Update clap
2017-04-05 17:42:06 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "a13e63ab62dbe32aeee58d1c5408d35c36c392bba5d9d3142287219721afe606"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"tinyvec",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Update clap
2017-04-05 17:42:06 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "unicode-width"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.1.8"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
[[package]]
name = "unicode-xid"
version = "0.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "8c1f860d7d29cf02cb2f3f359fd35991af3d30bac52c57d265a3c461074cb4dc"
Move from protobuf to bincode for a wire format This commit migrates away from the `protobuf` crate to instead just working with bincode on the wire as a serialization format. This is done by leveraging a few different crates: * The `bincode` and `serde_derive` crates are used to define serialization for Rust structures as well as provide a bincode implementation. * The `tokio_io::codec::length_delimited` module implements framing via length prefixes to transform an asynchronous stream of bytes into a literal `Stream` of `BytesMut`. * The `tokio_serde_bincode` crate is then used to tie it all together, parsing these `BytesMut` as the request/response types of sccache. Most of the changes here are related to moving away from the protobuf API throughout the codebase (e.g. `has_foo` and `take_foo`) towards a more rustic-ish API that just uses enums/structs. Overall it felt quite natural (as one would expect) to just use the raw enum/struct values. This may not be quite as performant as before but that doesn't really apply to sccache's use case where perf is hugely dominated by actually compiling and hashing, so I'm not too too worried about that. My personal motivation for this is twofold: 1. Using `protobuf` was a little clunky throughout the codebase and definitely had some sharp edges that felt good to smooth out. 2. There's currently what I believe some mysterious segfault and/or stray write happening in sccache and I'm not sure where. The `protobuf` crate had a lot of `unsafe` code and in lieu of actually auditing it I figured it'd be good to kill two birds with one stone. I have no idea if this fixes my segfault problem (I never could reproduce it) but I figured it's worth a shot.
2017-03-22 20:21:52 +03:00
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
[[package]]
name = "unicode-xid"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.2.1"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "f7fe0bb3479651439c9112f72b6c505038574c9fbb575ed1bf3b797fa39dd564"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
[[package]]
name = "unix_socket"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "6aa2700417c405c38f5e6902d699345241c28c0b7ade4abaad71e35a87eb1564"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"cfg-if 0.1.10",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"libc",
]
Add a Memcached cache variant This cache module uses a Memcached cluster. To make sccache use this, set SCCACHE_MEMCACHED to a list of tcp://<hostname>:<port> addresses, separated by whitespace.
2017-08-10 17:50:33 +03:00
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "untrusted"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a156c684c91ea7d62626509bce3cb4e1d9ed5c4d978f7b4352658f96a4c26b4a"
Rework sccache to use http rather than tcp
2018-07-12 02:38:16 +03:00
[[package]]
name = "url"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
version = "1.7.2"
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "dd4e7c0d531266369519a4aa4f399d748bd37043b00bde1e4ff1f60a120b355a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"idna 0.1.5",
"matches",
"percent-encoding 1.0.1",
]
Integrate the Tokio branch of Hyper This commit pulls in Hyper from its master branch which contains the asynchronous/Tokio integration. All instances of HTTP, namely when interacting with S3, are now all powered by async Hyper and work with futures rather than synchronous requests on thread pools.
2017-02-02 03:30:26 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
Update deps.
2019-12-10 00:17:20 +03:00
name = "url"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "2.2.0"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "5909f2b0817350449ed73e8bcd81c8c3c8d9a7a5d8acba4b27db277f1868976e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"form_urlencoded",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"idna 0.2.0",
"matches",
"percent-encoding 2.1.0",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
[[package]]
name = "utf8parse"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
version = "0.1.1"
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "8772a4ccbb4e89959023bc5b7cb8623a795caa7092d99f3aa9501b9484d4557d"
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "uuid"
Update deps.
2019-12-10 00:17:20 +03:00
version = "0.7.4"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "90dbc611eb48397705a6b0f6e917da23ae517e4d127123d2cf7674206627d32a"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"rand 0.6.5",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
Upgrade dependencies with semver bumps that don't require changes
2020-12-09 11:44:58 +03:00
[[package]]
name = "uuid"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9fde2f6a4bea1d6e007c4ad38c6839fa71cbb63b6dbf5b595aa38dc9b1093c11"
dependencies = [
"rand 0.7.3",
]
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "vcpkg"
Run `cargo update`
2020-12-22 01:20:34 +03:00
version = "0.2.11"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-22 01:20:34 +03:00
checksum = "b00bca6106a5e23f3eee943593759b7fcddb00554332e856d990c893966879fb"
Update ring
2018-01-07 18:33:04 +03:00
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "vec-arena"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eafc1b9b2dfc6f5529177b62cf806484db55b32dc7c9658a118e11bbeb33061d"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "vec_map"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.8.2"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Add a version check for bubblewrap in the server. Fixes #316
2019-07-18 08:03:39 +03:00
[[package]]
name = "version-compare"
Upgrade version-compare to 0.0.11
2020-12-08 10:56:42 +03:00
version = "0.0.11"
Add a version check for bubblewrap in the server. Fixes #316
2019-07-18 08:03:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade version-compare to 0.0.11
2020-12-08 10:56:42 +03:00
checksum = "1c18c859eead79d8b95d09e4678566e8d70105c4e7b251f707a03df32442661b"
Add a version check for bubblewrap in the server. Fixes #316
2019-07-18 08:03:39 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "version_check"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
version = "0.1.5"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
Update ring
2018-01-07 18:33:04 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "version_check"
`cargo update`
2020-06-11 04:40:05 +03:00
version = "0.9.2"
Update deps.
2019-12-10 00:17:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`cargo update`
2020-06-11 04:40:05 +03:00
checksum = "b5a972e5669d67ba988ce3dc826706fb0a8b01471c088cb0b6110b805cc36aed"
Update deps.
2019-12-10 00:17:20 +03:00
Make DiskCache limit the size of the on-disk cache by using LruDiskCache. Fixes #29
2016-11-29 03:59:42 +03:00
[[package]]
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
name = "void"
Make DiskCache limit the size of the on-disk cache by using LruDiskCache. Fixes #29
2016-11-29 03:59:42 +03:00
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
Update dependencies * Mostly upgrade to serde 1.0 * Pull in lots of other updates for other small deps
2017-05-18 23:53:00 +03:00
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
[[package]]
name = "vte"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
version = "0.3.3"
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "4f42f536e22f7fcbb407639765c8fd78707a33109301f834a594758bedd6e8cf"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"utf8parse",
]
Always request color output from rustc. Fixes #99 This change makes sccache run rustc with `--color=always`, removing any other --color option from the compiler options so that it's not included in the cache key. A `color_mode` method is added to the `CompilerHasher` trait, and the value is sent back to the client in the `CompileFinished` method, so the client can determine whether specific --color options were passed without having to do its own commandline parsing. The client uses the new `strip-ansi-escapes` crate to remove escape codes from the compiler output in situations where color output is not desired: * When `--color=never` was passed on the compiler commandline. * When `--color=auto` is in effect (the default) but the output is not a terminal. The existing cargo tests were lightly modified to run compile once with `--color=never` and once with `--color=always` to validate that cache hits are not affected by color options.
2018-02-02 15:11:11 +03:00
update test harness crates This patch looks like a routine crate version update, but it fixes something very fundamentally wrong with the tests: `escargot`, to find the `sccache` binary during tests, would actually run `cargo build` and parse the output. There were all manner of hacks to try and build the binary with the correct set of features, none of which were reliable, and the hacks were not reliably present in all places, either. When the hacks were not present, `escargot` would rebuild the entire sccache crate, which was responsible for the `sccache_cargo` test taking entirely too long. When the hacks failed utterly, perfectly fine patches would mysteriously fail, as seen in #774. We can get rid of `escargot` because `assert-cmd` has been updated to a) not use `escargot` under the hood; and b) do something smarter to locate the target binary. The upshot is fewer mysterious test failures and significantly faster running tests.
2020-06-05 01:34:11 +03:00
[[package]]
name = "wait-timeout"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f200f5b12eb75f8c1ed65abd4b2db8a6e1b138a20de009dacee265a2498f3f6"
dependencies = [
"libc",
]
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "waker-fn"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9d5b2c62b4012a3e1eca5a7e077d13b3bf498c4073e33ccd58626607748ceeca"
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
[[package]]
name = "walkdir"
version = "2.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "777182bc735b6424e1a57516d35ed72cb8019d85c8c9bf536dccb3445c1a2f7d"
dependencies = [
update walkdir 1 -> 2.3
2020-07-14 13:14:02 +03:00
"same-file",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"winapi-util",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
[[package]]
name = "want"
Re-balance timeouts to allow communicating with a scheduler to fall back appropriately.
2019-10-14 22:58:56 +03:00
version = "0.2.0"
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "b6395efa4784b027708f7451087e647ec73cc74f5d9bc2e418404248d679a230"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"futures 0.1.30",
"log 0.4.11",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
"try-lock",
]
refactor: Update hyper to 0.12 and use tokio Also updates request to 0.9 (as that uses hyper 0.12)
2018-09-27 17:30:22 +03:00
update jobserver crate version This change should help #578 not cause errors on the linux64 musl target...though why that target isn't failing *now*, with the older version of `jobserver` that we have, is something I don't understand
2019-11-04 19:05:43 +03:00
[[package]]
name = "wasi"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.9.0+wasi-snapshot-preview1"
update jobserver crate version This change should help #578 not cause errors on the linux64 musl target...though why that target isn't failing *now*, with the older version of `jobserver` that we have, is something I don't understand
2019-11-04 19:05:43 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
update jobserver crate version This change should help #578 not cause errors on the linux64 musl target...though why that target isn't failing *now*, with the older version of `jobserver` that we have, is something I don't understand
2019-11-04 19:05:43 +03:00
Run `cargo update`
2020-12-08 08:07:09 +03:00
[[package]]
name = "wasi"
version = "0.10.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "wasm-bindgen"
version = "0.2.69"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3cd364751395ca0f68cafb17666eee36b63077fb5ecd972bbcd74c90c4bf736e"
dependencies = [
"cfg-if 1.0.0",
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
version = "0.2.69"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1114f89ab1f4106e5b55e688b828c0ab0ea593a1ea7c094b141b14cbaaec2d62"
dependencies = [
"bumpalo",
"lazy_static",
"log 0.4.11",
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"wasm-bindgen-shared",
]
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "wasm-bindgen-futures"
version = "0.4.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1fe9756085a84584ee9457a002b7cdfe0bfff169f45d2591d8be1345a6780e35"
dependencies = [
"cfg-if 1.0.0",
"js-sys",
"wasm-bindgen",
"web-sys",
]
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
[[package]]
name = "wasm-bindgen-macro"
version = "0.2.69"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a6ac8995ead1f084a8dea1e65f194d0973800c7f571f6edd70adf06ecf77084"
dependencies = [
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
version = "0.2.69"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b5a48c72f299d80557c7c62e37e7225369ecc0c963964059509fbafe917c7549"
dependencies = [
"proc-macro2",
Run `cargo update`
2020-12-22 01:20:34 +03:00
"quote 1.0.8",
Run `cargo update`
2021-01-08 10:26:06 +03:00
"syn 1.0.58",
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
version = "0.2.69"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7e7811dd7f9398f14cc76efd356f98f03aa30419dea46aa810d71e819fc97158"
[[package]]
name = "web-sys"
version = "0.3.46"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "222b1ef9334f92a21d3fb53dc3fd80f30836959a90f9274a626d7e06315ba3c3"
dependencies = [
"js-sys",
"wasm-bindgen",
]
Revert "Upgrade redis to 0.18" This reverts commit 9189ac6bca240ae7973e2e626e3ef364c73bbe17. The upgrade to 0.18 requires a tokio 0.3 runtime, which we don't have, so despite building, it doesn't actually work.
2021-01-05 07:08:33 +03:00
[[package]]
name = "wepoll-sys"
version = "3.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0fcb14dea929042224824779fbc82d9fab8d2e6d3cbc0ac404de8edf489e77ff"
dependencies = [
"cc",
]
Started using which crate (#14)
2016-07-14 13:38:26 +03:00
[[package]]
name = "which"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "4.0.2"
switch back to released version of which, switch to a rusoto branch with a bug fix
2016-08-08 22:06:06 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "87c14ef7e1b8b8ecfc75d5eca37949410046e66f15d185c01d70824f1f8111ef"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
Upgrade dependencies that don't require changes Except redis, which pulls in async-std, which needs some further consideration.
2020-06-11 06:10:33 +03:00
"thiserror",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
Started using which crate (#14)
2016-07-14 13:38:26 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "winapi"
Update to a released rusoto, and 'cargo update' while we're at it
2016-07-15 18:06:16 +03:00
version = "0.2.8"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "winapi"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.3.9"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
Update ring
2018-01-07 18:33:04 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "winapi-i686-pc-windows-gnu"
cargo update
2018-02-01 18:29:23 +03:00
version = "0.4.0"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
Update ring
2018-01-07 18:33:04 +03:00
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
[[package]]
name = "winapi-util"
cargo update
2020-04-28 07:55:50 +03:00
version = "0.1.5"
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-28 07:55:50 +03:00
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
Update ring
2018-01-07 18:33:04 +03:00
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
cargo update
2018-02-01 18:29:23 +03:00
version = "0.4.0"
Update ring
2018-01-07 18:33:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Update ring
2018-01-07 18:33:04 +03:00
Update deps.
2019-12-10 00:17:20 +03:00
[[package]]
name = "winreg"
version = "0.6.2"
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "b2986deb581c4fe11b621998a5e53361efe6b48a151178d0cd9eeffa4dc6acc9"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"winapi 0.3.9",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
[[package]]
name = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"winapi 0.2.8",
"winapi-build",
]
Commit Cargo.lock
2016-05-12 22:03:37 +03:00
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
[[package]]
name = "xattr"
chore: Update predicates and assert_cmd
2018-08-28 14:29:00 +03:00
version = "0.2.2"
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
chore/cargo: convert Cargo.lock with cargo-lock
2020-03-18 18:07:45 +03:00
checksum = "244c3741f4240ef46274860397c7c74e50eb23624996930e484c16679633a54c"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
"libc",
]
Bits and pieces for distributed Rust
2018-04-12 04:25:15 +03:00
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
[[package]]
name = "zip"
Run `cargo update`
2020-12-08 08:07:09 +03:00
version = "0.5.9"
Implement fetching/storing to cache, interfaces for doing so, implement a disk cache
2016-05-21 21:14:26 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update`
2020-12-08 08:07:09 +03:00
checksum = "cc2896475a242c41366941faa27264df2cb935185a92e059a004d0048feb2ac5"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
dependencies = [
Run `cargo update`
2020-12-08 08:07:09 +03:00
"byteorder",
update to zip-rs 0.5 I was looking through old issues, and #160 mentioned that crc32 checksumming for zip files was showing up in profiles. zip-rs 0.4 uses a byte-at-a-time version of crc32; zip-rs 0.5 relies on the `crc32fast` crate, which features faster implementations.
2020-06-05 22:27:48 +03:00
"crc32fast",
Run `cargo update`
2020-12-08 08:07:09 +03:00
"thiserror",
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
]
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
[[package]]
name = "zstd"
Upgrade zstd to 0.6
2020-12-22 01:50:05 +03:00
version = "0.6.0+zstd.1.4.8"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade zstd to 0.6
2020-12-22 01:50:05 +03:00
checksum = "d4e44664feba7f2f1a9f300c1f6157f2d1bfc3c15c6f3cf4beabf3f5abe9c237"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
dependencies = [
"zstd-safe",
]
[[package]]
name = "zstd-safe"
Upgrade zstd to 0.6
2020-12-22 01:50:05 +03:00
version = "3.0.0+zstd.1.4.8"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade zstd to 0.6
2020-12-22 01:50:05 +03:00
checksum = "d9447afcd795693ad59918c7bbffe42fdd6e467d708f3537e3dc14dc598c573f"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
dependencies = [
"libc",
"zstd-sys",
]
[[package]]
name = "zstd-sys"
Upgrade zstd to 0.6
2020-12-22 01:50:05 +03:00
version = "1.4.19+zstd.1.4.8"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade zstd to 0.6
2020-12-22 01:50:05 +03:00
checksum = "ec24a9273d24437afb8e71b16f3d9a5d569193cccdb7896213b59f552f387674"
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
dependencies = [
"cc",
"glob",
Upgrade itertools to 0.10
2021-01-08 10:28:43 +03:00
"itertools 0.9.0",
use zstd to compress cache entries zstd is faster and gives slightly smaller (~5%) compressed blobs than deflate does, as measured on a Firefox build. Rather than inventing our own compressed archive format, we piggyback on top of zip's "stored" files to stuff zstd-compressed blobs in the zip archive.
2020-06-05 19:59:57 +03:00
"libc",
]