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

147 строки
4.9 KiB
TOML
Исходник Обычный вид История

Somewhat-fleshed-out skeleton. Has a protocol (defined in protocol.proto), client-server bits, and some basic request handling. Doesn't actually execute commands yet.
2016-04-26 23:43:03 +03:00
[package]
name = "sccache"
prepare new release
2022-10-16 22:45:55 +03:00
version = "0.3.1"
tweak Cargo.toml metadata and README
2017-05-25 19:46:37 +03:00
authors = ["Ted Mielczarek <ted@mielczarek.org>", "Alex Crichton <alex@alexcrichton.com>"]
Fix to enable cargo install
2016-12-16 03:55:19 +03:00
license = "Apache-2.0"
description = "Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible, storing a cache in a remote storage using the S3 API."
repository = "https://github.com/mozilla/sccache/"
tweak Cargo.toml metadata and README
2017-05-25 19:46:37 +03:00
readme = "README.md"
categories = ["command-line-utilities", "development-tools::build-utils"]
keywords = ["ccache"]
Transition to 2018 edition
2019-06-02 08:15:00 +03:00
edition = "2018"
update to Rust 1.60 as minimal version
2022-11-27 05:37:36 +03:00
rust-version = "1.60"
Fix to enable cargo install
2016-12-16 03:55:19 +03:00
Move all into single crate
2018-08-04 16:36:35 +03:00
[[bin]]
name = "sccache"
[[bin]]
name = "sccache-dist"
required-features = ["dist-server"]
Somewhat-fleshed-out skeleton. Has a protocol (defined in protocol.proto), client-server bits, and some basic request handling. Doesn't actually execute commands yet.
2016-04-26 23:43:03 +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 = "1.0"
Use different hashing functions for different file types (#1135) * Use different hashing functions for different file types This adds a new special hasher for static libraries, which contain timestamps and other info that prevent them from being cachable in some cases. * Update src/util.rs Co-authored-by: Mitchell Hentges <mitch9654@gmail.com> Co-authored-by: Jack Moffitt <jack@metajack.im> Co-authored-by: Mitchell Hentges <mitch9654@gmail.com>
2022-03-03 18:06:37 +03:00
ar = "0.9"
Migrate to stable Future trait and Tokio 0.2 Co-authored-by: Igor Matuszewski <xanewok@gmail.com>
2021-04-08 21:30:17 +03:00
async-trait = "0.1"
Fixes for updated deps, bump rouille, better logging
2018-09-04 22:36:28 +03:00
atty = "0.2.6"
Upgrade base64 to 0.13
2020-12-10 02:00:26 +03:00
base64 = "0.13"
chore: Update bincode to 1
2018-08-30 23:08:17 +03:00
bincode = "1"
Increase the MSRV and bump dependencies (#1137) * Bump the MSRV to 1.58 Bumps the official MSRV to 1.58. This is likely more than required the upcoming version bumps. * Upgrade cargo zstd to 0.10 * Bump serial_test to v0.6 Changelog does not mention any breaking changes. * Bump blake to v1 * Bump rouille to 3.5 Required to bump syslog to v6, since otherwise no common version can be selected for `time` * Bump syslog to v6 No changelog available. Depends on rouille bump to 3.5, to get a common version of ´time´. * Upgrade JWT to v8 The explicit insecure decode method was removed and replaced by an option for the Validation struct. The `exp` field had to be added to JobJwt, since otherwise the validation would fail at runtime. Apparently the `exp` field is required now, even if the valdiation of `exp` is turned off.
2022-05-05 17:47:19 +03:00
blake3 = "1"
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
byteorder = "1.0"
feat: Update tokio to 1.0 Followup on https://github.com/mozilla/sccache/pull/985 to pull sccache the last little bit into tokio 1.0
2021-11-12 15:28:26 +03:00
bytes = "1"
Bump chrono from 0.4.22 to 0.4.23 Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.22 to 0.4.23. - [Release notes](https://github.com/chronotope/chrono/releases) - [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md) - [Commits](https://github.com/chronotope/chrono/compare/v0.4.22...v0.4.23) --- updated-dependencies: - dependency-name: chrono dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-14 20:13:44 +03:00
chrono = { version = "0.4.23", optional = true }
Remove requirement on clap/derive
2022-04-01 06:38:11 +03:00
clap = { version = "3.2.22", features = ["derive", "env", "wrap_help"] }
Bump directories From Changelog: > BREAKING CHANGE The behavior of executable_dir has been > adjusted to not depend on $XDG_DATA_HOME. Code, which > assumed that setting the $XDG_DATA_HOME environment >variable also impacted executable_dir if the $XDG_BIN_HOME > environment variable was not set, requires adjustment. We do not appear to use the executable_dir() function, so this breaking change should not affect us. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2022-02-12 18:09:32 +03:00
directories = "4.0.1"
Bump env_logger From Changelog: >Breaking Changes: > > Default message format now prints the >target instead of the module Should not be so relevant, since I think sccache uses a custom logging format. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2022-02-12 18:02:37 +03:00
env_logger = "0.9"
chore: Update filetime to 0.2
2018-08-28 14:56:27 +03:00
filetime = "0.2"
Implement basic rust distributed compile
2018-09-04 22:36:28 +03:00
flate2 = { version = "1.0", optional = true, default-features = false, features = ["rust_backend"] }
Migrate to stable Future trait and Tokio 0.2 Co-authored-by: Igor Matuszewski <xanewok@gmail.com>
2021-04-08 21:30:17 +03:00
futures = "0.3"
Upgrade futures-locks to 0.7.0 0.7.0 only has 1 significant change that impacts us: RwLock is now only Sync if its inner type is also. Part of #1110.
2022-02-16 08:40:31 +03:00
futures-locks = "0.7"
Update gha-toolkit and docs
2022-11-30 08:33:50 +03:00
gha-toolkit = { version = "0.3.1", optional = true }
Update winapi Drops kernel-sys from the dependency tree and winapi duplicates. Closes #1163
2022-11-29 20:32:24 +03:00
gzp = { version = "0.11", default-features = false, features = ["deflate_rust"] }
Bump hmac, sha-1 and sha2 (#1117) The crypto crates are interdependent so bump them in one go. It looks like `new_varkey()` was renamed to `new_from_slice()`, at least that is what I gather from the changed example in the documentation of the hmac crate between version 0.11 and 0.10. See https://docs.rs/hmac/0.11.0/hmac/index.html The changelog doesn't mention anything of the sort. Also I'm not sure if the S3 version even works anymore, since I think AWS requires the v4 authentication scheme now and not the older v2 version used in simples3. It would probably make sense to use the new aws-sdk or one of its subcrates. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2022-02-14 22:44:46 +03:00
hmac = { version = "0.12.0", optional = true }
Migrate to stable Future trait and Tokio 0.2 Co-authored-by: Igor Matuszewski <xanewok@gmail.com>
2021-04-08 21:30:17 +03:00
http = "0.2"
Require openssl >= 0.10.9
2022-11-27 05:41:29 +03:00
hyper = { version = "0.14.10", optional = true, features = ["server"] }
Update hyperx MSRV for 1.4 is 1.46 Breaking change in v0.14 to `Header::parse_header`. Since the `HeaderValue` directly implements RawLike trait, we can just use it as is, without converting. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2022-02-12 20:46:53 +03:00
hyperx = { version = "1.0", optional = true }
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
jobserver = "0.1"
Increase the MSRV and bump dependencies (#1137) * Bump the MSRV to 1.58 Bumps the official MSRV to 1.58. This is likely more than required the upcoming version bumps. * Upgrade cargo zstd to 0.10 * Bump serial_test to v0.6 Changelog does not mention any breaking changes. * Bump blake to v1 * Bump rouille to 3.5 Required to bump syslog to v6, since otherwise no common version can be selected for `time` * Bump syslog to v6 No changelog available. Depends on rouille bump to 3.5, to get a common version of ´time´. * Upgrade JWT to v8 The explicit insecure decode method was removed and replaced by an option for the Validation struct. The `exp` field had to be added to JobJwt, since otherwise the validation would fail at runtime. Apparently the `exp` field is required now, even if the valdiation of `exp` is turned off.
2022-05-05 17:47:19 +03:00
jsonwebtoken = { version = "8", optional = true }
Fixes for updated deps, bump rouille, better logging
2018-09-04 22:36:28 +03:00
lazy_static = "1.0.0"
Bump libc from 0.2.135 to 0.2.137 (#1373) Bumps [libc](https://github.com/rust-lang/libc) from 0.2.135 to 0.2.137. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.135...0.2.137) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-11-09 09:28:20 +03:00
libc = "0.2.137"
Move lru-disk-cache to an internal module See discussion in #916
2021-01-07 08:08:48 +03:00
linked-hash-map = "0.5"
chore: Update log to 0.4 and env_logger to 0.5
2018-08-28 14:41:11 +03:00
log = "0.4"
Bump md-5 from 0.10.4 to 0.10.5 (#1331) Bumps [md-5](https://github.com/RustCrypto/hashes) from 0.10.4 to 0.10.5. - [Release notes](https://github.com/RustCrypto/hashes/releases) - [Commits](https://github.com/RustCrypto/hashes/compare/md-5-v0.10.4...md-5-v0.10.5) --- updated-dependencies: - dependency-name: md-5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-09-23 23:39:24 +03:00
md-5 = { version = "0.10.5", optional = true }
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
memcached-rs = { version = "0.4" , optional = true }
Bump num_cpus from 1.13.1 to 1.14.0 Bumps [num_cpus](https://github.com/seanmonstar/num_cpus) from 1.13.1 to 1.14.0. - [Release notes](https://github.com/seanmonstar/num_cpus/releases) - [Changelog](https://github.com/seanmonstar/num_cpus/blob/master/CHANGELOG.md) - [Commits](https://github.com/seanmonstar/num_cpus/compare/v1.13.1...v1.14.0) --- updated-dependencies: - dependency-name: num_cpus dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 20:07:59 +03:00
num_cpus = "1.14"
Upgrade number_prefix to 0.4
2020-12-10 02:03:49 +03:00
number_prefix = "0.4"
Require openssl >= 0.10.9
2022-11-27 05:41:29 +03:00
openssl = { version = "0.10.9", optional = true }
Upgrade url to 2.2
2020-12-10 01:19:22 +03:00
percent-encoding = { version = "2", optional = true }
Bump rand to 0.8 The changelog is pretty detailed, but at a first glance I can't notice any relevant looking changes that might be breaking. tests are passing. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2022-02-12 18:20:14 +03:00
rand = "0.8.4"
Bump regex from 1.6.0 to 1.7.0 Bumps [regex](https://github.com/rust-lang/regex) from 1.6.0 to 1.7.0. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.6.0...1.7.0) --- updated-dependencies: - dependency-name: regex dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-08 20:06:46 +03:00
regex = "1.7.0"
Replace usages of blocking `reqwest` to be async instead (#1164) * Replace `dist-client` usages of blocking `reqwest` to be async instead The blocking implementation of `reqwest` now uses an internal `tokio` runtime as of `0.10`. `tokio` doesn't like having nested runtimes, so it raises an error when `request>=0.10` is used from a tokio-`async` function. The primary rationale for continuing to use "blocking" `reqwest` was because its async implementation was "extremely limited" and didn't support streamed data from a file. However, now, we're able to leverage `tokio::fs::File -> AsyncRead -> ReaderStream -> Body::wrap_stream()`, which obsoletes this one use case for blocking `reqwest`. Convert all blocking usages of `reqwest` to `async` accordingly. Fixes #1161. * Avoid nested `tokio` runtime in `create_state()` `tokio` doesn't allow for nested runtimes, yet `create_state` is a non-async function that needs to run nested async code. I'm not sure _exactly_ how this ran successfully before, but I'm guessing that the updated `tokio` was stricter about nested runtimes. Either way, work around this by manually reusing the current thread's runtime with `Handle::try_current().enter()`. If no existing handle exists (such as when `create_state()` is called from entirely-non-async-code), then manually use `config.pool` again.
2022-04-26 18:14:57 +03:00
reqwest = { version = "0.11", features = ["json", "blocking", "stream"], optional = true }
Bump retry from 1.3.1 to 2.0.0 Bumps [retry](https://github.com/jimmycuadra/retry) from 1.3.1 to 2.0.0. - [Release notes](https://github.com/jimmycuadra/retry/releases) - [Commits](https://github.com/jimmycuadra/retry/compare/1.3.1...2.0.0) --- updated-dependencies: - dependency-name: retry dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-19 20:44:22 +03:00
retry = "2"
Upgrade ring to 0.16 and jsonwebtoken to 7
2020-12-09 10:46:21 +03:00
ring = { version = "0.16", optional = true, features = ["std"] }
make url part of redis feature, alias redis as rredis (#1226) Closes #1225
2022-07-16 11:20:36 +03:00
rredis = { package = "redis", version = "0.21", optional = true, default-features = false, features = ["aio", "tokio-comp", "tokio-native-tls-comp"] }
bump semver to 1.0.0 Since memcached-rs still depends on 0.9.0, this adds an extra dependency to be compiled. Upstream already included the semver bump but no release was slated so far.
2022-08-04 12:13:04 +03:00
semver = "1.0"
Bump sha-1 from 0.10.0 to 0.10.1 Bumps [sha-1](https://github.com/RustCrypto/hashes) from 0.10.0 to 0.10.1. - [Release notes](https://github.com/RustCrypto/hashes/releases) - [Commits](https://github.com/RustCrypto/hashes/compare/sha-1-v0.10.0...md2-v0.10.1) --- updated-dependencies: - dependency-name: sha-1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-28 20:13:01 +03:00
sha-1 = { version = "0.10.1", optional = true }
Bump sha2 from 0.10.5 to 0.10.6 (#1323) Bumps [sha2](https://github.com/RustCrypto/hashes) from 0.10.5 to 0.10.6. - [Release notes](https://github.com/RustCrypto/hashes/releases) - [Commits](https://github.com/RustCrypto/hashes/compare/sha2-v0.10.5...sha2-v0.10.6) --- updated-dependencies: - dependency-name: sha2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-09-16 22:39:02 +03:00
sha2 = { version = "0.10.6", optional = true }
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
serde = "1.0"
serde_derive = "1.0"
Fix build with --no-default-features --features=redis The serde_json crate is always needed by src/commands.rs even when building only with support for Redis, but serde_json would be left out when the S3 feature is disabled. This make it possible to build sccache only with Redis support. Building with S3 disabled trims down a stripped release build from 5.1 MiB down to 4.4 MiB on x86_64.
2017-06-14 12:43:05 +03:00
serde_json = "1.0"
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
strip-ansi-escapes = "0.1"
Require openssl >= 0.10.9
2022-11-27 05:41:29 +03:00
tar = "0.4.36"
chore: Update tempfile to 3
2018-08-28 15:20:49 +03:00
tempfile = "3"
feat: Update tokio to 1.0 Followup on https://github.com/mozilla/sccache/pull/985 to pull sccache the last little bit into tokio 1.0
2021-11-12 15:28:26 +03:00
tokio = { version = "1", features = ["rt-multi-thread", "io-util", "time", "net", "process", "macros"] }
tokio-serde = "0.8"
Bump tokio-util from 0.6.9 to 0.7.3 (#1218) Bumps [tokio-util](https://github.com/tokio-rs/tokio) from 0.6.9 to 0.7.3. - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](https://github.com/tokio-rs/tokio/compare/tokio-util-0.6.9...tokio-util-0.7.3) --- updated-dependencies: - dependency-name: tokio-util dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-06-23 22:07:33 +03:00
tokio-util = { version = "0.7", features = ["codec", "io"] }
feat: Update tokio to 1.0 Followup on https://github.com/mozilla/sccache/pull/985 to pull sccache the last little bit into tokio 1.0
2021-11-12 15:28:26 +03:00
tower = "0.4"
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
toml = "0.5"
Upgrade url to 2.2
2020-12-10 01:19:22 +03:00
url = { version = "2", optional = true }
Bump uuid from 1.1.2 to 1.2.1 Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.1.2 to 1.2.1. - [Release notes](https://github.com/uuid-rs/uuid/releases) - [Commits](https://github.com/uuid-rs/uuid/compare/1.1.2...1.2.1) --- updated-dependencies: - dependency-name: uuid dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-10-11 20:45:49 +03:00
uuid = { version = "1.2", features = ["v4"] }
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
walkdir = "2"
involve rustup when determining toolchain paths (#666) Co-authored-by: Bernhard Schuster <bernhard@workwork.parity1>
2020-03-20 22:13:32 +03:00
# by default which pulls in an outdated failure version
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
which = { version = "4", default-features = false }
Bump zip from 0.5.13 to 0.6.0 (#1210) Bumps [zip](https://github.com/zip-rs/zip) from 0.5.13 to 0.6.0. - [Release notes](https://github.com/zip-rs/zip/releases) - [Commits](https://github.com/zip-rs/zip/commits/v0.6) --- updated-dependencies: - dependency-name: zip dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-06-23 09:57:54 +03:00
zip = { version = "0.6", default-features = false }
Bump zstd from 0.11.2+zstd.1.5.2 to 0.12.0+zstd.1.5.2 Bumps [zstd](https://github.com/gyscos/zstd-rs) from 0.11.2+zstd.1.5.2 to 0.12.0+zstd.1.5.2. - [Release notes](https://github.com/gyscos/zstd-rs/releases) - [Commits](https://github.com/gyscos/zstd-rs/commits) --- updated-dependencies: - dependency-name: zstd dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-23 20:09:48 +03:00
zstd = "0.12"
Support running compile commands on the server. This change lets the server run compile commands for supported compilers. It doesn't do any output caching yet, but if it detects that a commandline is a supported compiler it will send a `CompileStarted` message to the client, run the compiler on a background thread, and then send a `CompileFinished` message with the exit status and stdout/stderr when it completes.
2016-05-12 21:47:46 +03:00
Fixes for updated deps, bump rouille, better logging
2018-09-04 22:36:28 +03:00
# dist-server only
Upgrade crossbeam
2020-10-07 05:42:26 +03:00
crossbeam-utils = { version = "0.8", optional = true }
Move all into single crate
2018-08-04 16:36:35 +03:00
libmount = { version = "0.1.10", optional = true }
Bump nix from 0.24.2 to 0.25.0 Bumps [nix](https://github.com/nix-rust/nix) from 0.24.2 to 0.25.0. - [Release notes](https://github.com/nix-rust/nix/releases) - [Changelog](https://github.com/nix-rust/nix/blob/master/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.24.2...v0.25.0) --- updated-dependencies: - dependency-name: nix dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-15 20:45:30 +03:00
nix = { version = "0.25.0", optional = true }
Increase the MSRV and bump dependencies (#1137) * Bump the MSRV to 1.58 Bumps the official MSRV to 1.58. This is likely more than required the upcoming version bumps. * Upgrade cargo zstd to 0.10 * Bump serial_test to v0.6 Changelog does not mention any breaking changes. * Bump blake to v1 * Bump rouille to 3.5 Required to bump syslog to v6, since otherwise no common version can be selected for `time` * Bump syslog to v6 No changelog available. Depends on rouille bump to 3.5, to get a common version of ´time´. * Upgrade JWT to v8 The explicit insecure decode method was removed and replaced by an option for the Validation struct. The `exp` field had to be added to JobJwt, since otherwise the validation would fail at runtime. Apparently the `exp` field is required now, even if the valdiation of `exp` is turned off.
2022-05-05 17:47:19 +03:00
rouille = { version = "3.5", optional = true, default-features = false, features = ["ssl"] }
syslog = { version = "6", optional = true }
Add tests, remove unwraps, fix bugs, auto https
2018-10-26 22:34:03 +03:00
void = { version = "1", optional = true }
Bump version-compare from 0.1.0 to 0.1.1 (#1394) Bumps [version-compare](https://gitlab.com/timvisee/version-compare) from 0.1.0 to 0.1.1. - [Release notes](https://gitlab.com/timvisee/version-compare/tags) - [Changelog](https://gitlab.com/timvisee/version-compare/blob/master/CHANGELOG.md) - [Commits](https://gitlab.com/timvisee/version-compare/compare/v0.1.0...v0.1.1) --- updated-dependencies: - dependency-name: version-compare dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-11-10 23:02:21 +03:00
version-compare = { version = "0.1.1", optional = true }
Add tests, remove unwraps, fix bugs, auto https
2018-10-26 22:34:03 +03:00
Update aws-* crates to latest version
2022-11-14 08:25:38 +03:00
aws-config = { version = "0.51", optional = true }
aws-sdk-s3 = { version = "0.21", optional = true }
aws-types = { version = "0.51", optional = true }
aws-smithy-client = { version = "0.51", features = ["rustls"], optional = true }
aws-sig-auth = { version = "0.51", optional = true }
New S3 backend The backend uses the official AWS SDK for Rust. It supports SCCACHE_BUCKET, SCCACHE_REGION and SCCACHE_ENDPOINT like the old backend. It does not support SCCACHE_S3_USE_SSL. The backend adds support for a new SCCACHE_S3_NO_CREDENTIALS key that can be set to implement a readonly cache that does not require AWS credentials at all. This is useful to speed up public pull request builds that typically can't access AWS credentials for security reasons.
2022-01-03 03:22:14 +03:00
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
[dev-dependencies]
Bump assert_cmd from 2.0.4 to 2.0.5 Bumps [assert_cmd](https://github.com/assert-rs/assert_cmd) from 2.0.4 to 2.0.5. - [Release notes](https://github.com/assert-rs/assert_cmd/releases) - [Changelog](https://github.com/assert-rs/assert_cmd/blob/master/CHANGELOG.md) - [Commits](https://github.com/assert-rs/assert_cmd/compare/v2.0.4...v2.0.5) --- updated-dependencies: - dependency-name: assert_cmd dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-10-20 20:41:51 +03:00
assert_cmd = "=2.0.5"
switch from the gcc crate to its successor, cc, for tests
2018-02-01 18:35:56 +03:00
cc = "1.0"
Require openssl >= 0.10.9
2022-11-27 05:41:29 +03:00
chrono = "0.4.22"
Upgrade itertools to 0.10
2021-01-08 10:28:43 +03:00
itertools = "0.10"
Bump predicates from 2.1.1 to 2.1.2 Bumps [predicates](https://github.com/assert-rs/predicates-rs) from 2.1.1 to 2.1.2. - [Release notes](https://github.com/assert-rs/predicates-rs/releases) - [Changelog](https://github.com/assert-rs/predicates-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/assert-rs/predicates-rs/compare/v2.1.1...v2.1.2) --- updated-dependencies: - dependency-name: predicates dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 20:07:50 +03:00
predicates = "=2.1.2"
Migrate to a Tokio 1.0-capable Selenium webdriver crate We don't actually use the auth0 ourselves but it's nice to prune so many dependency crates by not using old reqwest/tokio crates.
2021-12-06 19:22:21 +03:00
thirtyfour_sync = "0.27"
Bump once_cell from 1.15.0 to 1.16.0 Bumps [once_cell](https://github.com/matklad/once_cell) from 1.15.0 to 1.16.0. - [Release notes](https://github.com/matklad/once_cell/releases) - [Changelog](https://github.com/matklad/once_cell/blob/master/CHANGELOG.md) - [Commits](https://github.com/matklad/once_cell/compare/v1.15.0...v1.16.0) --- updated-dependencies: - dependency-name: once_cell dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-10-31 21:20:19 +03:00
once_cell = "1.16"
Bump serial_test from 0.8.0 to 0.9.0 (#1279) Bumps [serial_test](https://github.com/palfrey/serial_test) from 0.8.0 to 0.9.0. - [Release notes](https://github.com/palfrey/serial_test/releases) - [Commits](https://github.com/palfrey/serial_test/compare/v0.8.0...v0.9.0) --- updated-dependencies: - dependency-name: serial_test dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-08-11 11:13:27 +03:00
serial_test = "0.9"
Bump wiremock from 0.5.14 to 0.5.15 Bumps [wiremock](https://github.com/LukeMathWalker/wiremock-rs) from 0.5.14 to 0.5.15. - [Release notes](https://github.com/LukeMathWalker/wiremock-rs/releases) - [Changelog](https://github.com/LukeMathWalker/wiremock-rs/blob/main/CHANGELOG.md) - [Commits](https://github.com/LukeMathWalker/wiremock-rs/compare/v0.5.14...v0.5.15) --- updated-dependencies: - dependency-name: wiremock dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-10-11 20:46:03 +03:00
wiremock = "0.5.15"
When hashing Rust compile arguments, sort -L and --cfg args as well as --extern
2017-04-03 17:21:13 +03:00
daemonize the server process on unix
2016-10-26 23:22:52 +03:00
[target.'cfg(unix)'.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
daemonize = "0.4"
daemonize the server process on unix
2016-10-26 23:22:52 +03:00
Use a named unix socket or named pipe to let the background server notify the client that it started successfully
2017-01-27 22:39:47 +03:00
[target.'cfg(windows)'.dependencies]
feat: Update tokio to 1.0 Followup on https://github.com/mozilla/sccache/pull/985 to pull sccache the last little bit into tokio 1.0
2021-11-12 15:28:26 +03:00
parity-tokio-ipc = "0.9"
Use a named unix socket or named pipe to let the background server notify the client that it started successfully
2017-01-27 22:39:47 +03:00
Remove usage of kernel32-sys crate
2019-06-21 20:44:38 +03:00
[target.'cfg(windows)'.dependencies.winapi]
version = "0.3"
features = [
"fileapi",
"handleapi",
Remove the dependency on the local-encoding crate The local-encoding crate was used to convert Windows paths using the user machine's OEM codepoint. This functionality is very small and was easily folded in the code that requires it. Removing this crate cuts 11 crates from sccache dependencies including many very old and unmaintained ones.
2022-10-28 10:44:05 +03:00
"stringapiset",
Remove usage of kernel32-sys crate
2019-06-21 20:44:38 +03:00
"winnls",
]
Don't create consoles for compiler invocations on Windows. Fixes #16. This fixes the extra console windows that show up when the sccache server creates compiler processes on Windows, but it only works on nightly Rust currently, and requires building with `--features=unstable`, because it relies on the not-yet-stable `windows_process_extensions` feature (https://github.com/rust-lang/rust/issues/37827). Also I added a bunch of extra documentation to the mock_command traits.
2016-12-13 17:44:20 +03:00
[features]
Enable everything but dist-server by default
2020-12-10 04:17:57 +03:00
default = ["all"]
Build the distributed compilation client support by default. Fixes #383
2019-04-03 18:06:48 +03:00
all = ["dist-client", "redis", "s3", "memcached", "gcs", "azure"]
Add reqwest to azure feature. Fixes #967
2021-03-02 14:43:29 +03:00
azure = ["chrono", "hyper", "hyperx", "reqwest", "url", "hmac", "md-5", "sha2"]
New S3 backend The backend uses the official AWS SDK for Rust. It supports SCCACHE_BUCKET, SCCACHE_REGION and SCCACHE_ENDPOINT like the old backend. It does not support SCCACHE_S3_USE_SSL. The backend adds support for a new SCCACHE_S3_NO_CREDENTIALS key that can be set to implement a readonly cache that does not require AWS credentials at all. This is useful to speed up public pull request builds that typically can't access AWS credentials for security reasons.
2022-01-03 03:22:14 +03:00
s3 = ["aws-config", "aws-sdk-s3", "aws-types", "aws-smithy-client", "aws-sig-auth"]
Remove unused dependency "untrusted" There seems to be no place using it, so lets just remove it. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2022-02-12 19:06:53 +03:00
gcs = ["chrono", "hyper", "hyperx", "percent-encoding", "reqwest", "ring", "url"]
Add support for GitHub Actions cache
2022-10-05 12:49:39 +03:00
gha = ["gha-toolkit"]
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
memcached = ["memcached-rs"]
Add a dummy native-zlib feature for backwards compatibility
2020-12-11 03:54:09 +03:00
native-zlib = []
make url part of redis feature, alias redis as rredis (#1226) Closes #1225
2022-07-16 11:20:36 +03:00
redis = ["url", "rredis"]
Don't create consoles for compiler invocations on Windows. Fixes #16. This fixes the extra console windows that show up when the sccache server creates compiler processes on Windows, but it only works on nightly Rust currently, and requires building with `--features=unstable`, because it relies on the not-yet-stable `windows_process_extensions` feature (https://github.com/rust-lang/rust/issues/37827). Also I added a bunch of extra documentation to the mock_command traits.
2016-12-13 17:44:20 +03:00
# Enable features that require unstable features of Nightly Rust.
unstable = []
Feature flag toggle for distributed compilation, cleanups
2018-07-31 01:06:14 +03:00
# Enables distributed support in the sccache client
Use different hashing functions for different file types (#1135) * Use different hashing functions for different file types This adds a new special hasher for static libraries, which contain timestamps and other info that prevent them from being cachable in some cases. * Update src/util.rs Co-authored-by: Mitchell Hentges <mitch9654@gmail.com> Co-authored-by: Jack Moffitt <jack@metajack.im> Co-authored-by: Mitchell Hentges <mitch9654@gmail.com>
2022-03-03 18:06:37 +03:00
dist-client = ["flate2", "hyper", "hyperx", "reqwest", "url", "sha2"]
Move all into single crate
2018-08-04 16:36:35 +03:00
# Enables the sccache-dist binary
fix(build): dist-server without any other features
2020-08-17 23:16:37 +03:00
dist-server = ["crossbeam-utils", "jsonwebtoken", "flate2", "hyperx", "libmount", "nix", "openssl", "reqwest", "rouille", "syslog", "void", "version-compare"]
Selenium tests for oauth
2018-10-23 10:33:42 +03:00
# Enables dist tests with external requirements
Added dependency of dist-tests on dist-client and dist-server
2019-11-11 16:02:58 +03:00
dist-tests = ["dist-client", "dist-server"]
Don't create consoles for compiler invocations on Windows. Fixes #16. This fixes the extra console windows that show up when the sccache server creates compiler processes on Windows, but it only works on nightly Rust currently, and requires building with `--features=unstable`, because it relies on the not-yet-stable `windows_process_extensions` feature (https://github.com/rust-lang/rust/issues/37827). Also I added a bunch of extra documentation to the mock_command traits.
2016-12-13 17:44: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
[workspace]
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
exclude = ["tests/test-crate"]