thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-17 21:24:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
82fc51ffa6
ClickHouse/rust/Cargo.lock

1546 lines
38 KiB
Plaintext
Raw Normal View History

Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "_ch_rust_blake3"
version = "0.1.0"
dependencies = [
"blake3",
"libc",
]
[[package]]
name = "_ch_rust_prql"
version = "0.1.0"
dependencies = [
"prql-compiler",
"serde_json",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "_ch_rust_skim_rust"
version = "0.1.0"
dependencies = [
"cxx",
"cxx-build",
"skim",
skim: do not panic if terminal is not available Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-14 15:45:00 +00:00
"term",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "addr2line"
version = "0.20.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4fa78e18c64fce05e902adecd7a5eed15a5e0a3439f7b0e169f0252214865e3"
dependencies = [
"gimli",
]
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
[[package]]
name = "ahash"
version = "0.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fcb51a0695d8f838b1ee009b3fbf66bda078cd64590202a864a8f3e8c4315c47"
dependencies = [
"getrandom",
"once_cell",
"version_check",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "aho-corasick"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.0.2"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "43f6cb1bf222025340178f382c426f13757b2960e89779dfcb319c32542a5a41"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"memchr",
]
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
[[package]]
name = "android-tzdata"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e999941b234f3131b00bc13c22d06e8c5ff726d1b6318ac7eb276997bbb4fef0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "android_system_properties"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
dependencies = [
"libc",
]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "anstream"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ca84f3628370c59db74ee214b3263d58f9aadd9b4fe7e711fd87dc452b7f163"
dependencies = [
"anstyle",
"anstyle-parse",
"anstyle-query",
"anstyle-wincon",
"colorchoice",
"is-terminal",
"utf8parse",
]
[[package]]
name = "anstyle"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3a30da5c5f2d5e72842e00bcb57657162cdabef0931f40e2deb9b4140440cecd"
[[package]]
name = "anstyle-parse"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "938874ff5980b03a87c5524b3ae5b59cf99b1d6bc836848df7bc5ada9643c333"
dependencies = [
"utf8parse",
]
[[package]]
name = "anstyle-query"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5ca11d4be1bab0c8bc8734a9aa7bf4ee8316d462a08c6ac5052f888fef5b494b"
dependencies = [
"windows-sys",
]
[[package]]
name = "anstyle-wincon"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "180abfa45703aebe0093f79badacc01b8fd4ea2e35118747e5811127f926e188"
dependencies = [
"anstyle",
"windows-sys",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "anyhow"
version = "1.0.72"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3b13c32d80ecc7ab747b80c3784bce54ee8a7a0cc4fbda9bf4cda2cf6fe90854"
dependencies = [
"backtrace",
]
[[package]]
name = "ariadne"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
version = "0.3.0"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "72fe02fc62033df9ba41cba57ee19acf5e742511a140c7dbc3a873e19a19a1bd"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
"unicode-width",
"yansi",
]
[[package]]
name = "arrayref"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6b4930d2cb77ce62f89ee5d5289b4ac049559b1c45539271f5ed4fdc7db34545"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "arrayvec"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.7.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "96d30a06541fbafbc7f82ed10c06164cfbd2c401138f6addd8404629c4b16711"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "autocfg"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "backtrace"
version = "0.3.68"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4319208da049c43661739c5fade2ba182f09d1dc2299b32298d3a31692b17e12"
dependencies = [
"addr2line",
"cc",
"cfg-if",
"libc",
"miniz_oxide",
"object",
"rustc-demangle",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "beef"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3a8241f3ebb85c056b509d4327ad0358fbbba6ffb340bf388f26350aeda225b1"
[[package]]
name = "bitflags"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "bitflags"
version = "2.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "630be753d4e58660abd17930c71b647fe46c27ea6b63cc59e1e3851406972e42"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "blake3"
version = "1.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "199c42ab6972d92c9f8995f086273d25c42fc0f7b2a1fcefba465c1352d25ba5"
dependencies = [
"arrayref",
"arrayvec",
"cc",
"cfg-if",
"constant_time_eq",
"digest",
]
[[package]]
name = "block-buffer"
version = "0.10.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
dependencies = [
"generic-array",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "bumpalo"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "3.13.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "a3e2c3daef883ecc1b5d58c15adae93470a91d425f3532ba1695849656af3fc1"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "cc"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.0.79"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "50d30906286121d95be3d479533b458f87493b30a4b5f79a607db8f5d11aa91f"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
[[package]]
name = "chrono"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.4.26"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "ec837a71355b28f6556dbd569b37b3f363091c0bd4b2e735674521b4c5fd9bc5"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"android-tzdata",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"iana-time-zone",
"js-sys",
"num-traits",
"time 0.1.45",
"wasm-bindgen",
"winapi",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "chumsky"
version = "0.9.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "23170228b96236b5a7299057ac284a321457700bc8c41a4476052f0f4ba5349d"
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"hashbrown",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"stacker",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "codespan-reporting"
version = "0.11.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3538270d33cc669650c4b093848450d380def10c331d38c768e34cac80576e6e"
dependencies = [
"termcolor",
"unicode-width",
]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "colorchoice"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "acbf1af155f9b9ef647e42cdc158db4b64a1b61f743629225fde6f3e0be2a7c7"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "constant_time_eq"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7144d30dcf0fafbce74250a3963025d8d52177934239851c917d29f1df280c2"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "core-foundation-sys"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.8.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "e496a50fda8aacccc86d7529e2c1e0892dbd0f898a6b5645b5561b89c3210efa"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "crossbeam"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2801af0d36612ae591caa9568261fddce32ce6e08a7275ea334a06a4ad021a2c"
dependencies = [
"cfg-if",
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-epoch",
"crossbeam-queue",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-channel"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.5.8"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cfg-if",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-deque"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.8.3"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "ce6fd6f855243022dcecf8702fef0c297d4338e226845fe067f6341ad9fa0cef"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cfg-if",
"crossbeam-epoch",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-epoch"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.9.15"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "ae211234986c545741a7dc064309f67ee1e5ad243d0e48335adc0484d960bcc7"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"autocfg",
"cfg-if",
"crossbeam-utils",
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"memoffset 0.9.0",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"scopeguard",
]
[[package]]
name = "crossbeam-queue"
version = "0.3.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d1cfb3ea8a53f37c40dea2c7bedcbd88bdfae54f5e2175d6ecaff1c988353add"
dependencies = [
"cfg-if",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-utils"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.8.16"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "5a22b2d63d4d1dc0b7f1b6b2747dd0088008a9be28b6ddf0b1e7d335e3037294"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cfg-if",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "crypto-common"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
dependencies = [
"generic-array",
"typenum",
]
[[package]]
name = "csv"
version = "1.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "626ae34994d3d8d668f4269922248239db4ae42d538b14c398b74a52208e8086"
dependencies = [
"csv-core",
"itoa",
"ryu",
"serde",
]
[[package]]
name = "csv-core"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2b2466559f260f48ad25fe6317b3c8dac77b5bdb5763ac7d9d6103530663bc90"
dependencies = [
"memchr",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "cxx"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.102"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "f68e12e817cb19eaab81aaec582b4052d07debd3c3c6b083b9d361db47c7dc9d"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cc",
"cxxbridge-flags",
"cxxbridge-macro",
"link-cplusplus",
]
[[package]]
name = "cxx-build"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.102"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "e789217e4ab7cf8cc9ce82253180a9fe331f35f5d339f0ccfe0270b39433f397"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cc",
"codespan-reporting",
"once_cell",
"proc-macro2",
"quote",
"scratch",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"syn 2.0.27",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "cxxbridge-flags"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.102"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "78a19f4c80fd9ab6c882286fa865e92e07688f4387370a209508014ead8751d0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "cxxbridge-macro"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.102"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "b8fcfa71f66c8563c4fa9dd2bb68368d50267856f831ac5d85367e0805f9606c"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"proc-macro2",
"quote",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"syn 2.0.27",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "darling"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.14.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "7b750cb3417fd1b327431a470f388520309479ab0bf5e323505daf0290cd3850"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"darling_core",
"darling_macro",
]
[[package]]
name = "darling_core"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.14.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "109c1ca6e6b7f82cc233a97004ea8ed7ca123a9af07a8230878fcfda9b158bf0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
"strsim",
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"syn 1.0.109",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "darling_macro"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.14.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "a4aab4dbc9f7611d8b55048a3a16d2d010c2c8334e46304b40ac1cc14bf3b48e"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"darling_core",
"quote",
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"syn 1.0.109",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "defer-drop"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f613ec9fa66a6b28cdb1842b27f9adf24f39f9afc4dcdd9fdecee4aca7945c57"
dependencies = [
"crossbeam-channel",
"once_cell",
]
[[package]]
name = "derive_builder"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d07adf7be193b71cc36b193d0f5fe60b918a3a9db4dad0449f57bcfd519704a3"
dependencies = [
"derive_builder_macro",
]
[[package]]
name = "derive_builder_core"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1f91d4cfa921f1c05904dc3c57b4a32c38aed3340cce209f3a6fd1478babafc4"
dependencies = [
"darling",
"proc-macro2",
"quote",
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"syn 1.0.109",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "derive_builder_macro"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f0314b72bed045f3a68671b3c86328386762c93f82d98c65c3cb5e5f573dd68"
dependencies = [
"derive_builder_core",
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"syn 1.0.109",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "digest"
version = "0.10.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
dependencies = [
"block-buffer",
"crypto-common",
"subtle",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "dirs-next"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b98cf8ebf19c3d1b223e151f99a4f9f0690dca41414773390fc824184ac833e1"
dependencies = [
"cfg-if",
"dirs-sys-next",
]
[[package]]
name = "dirs-sys-next"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4ebda144c4fe02d1f7ea1a7d9641b6fc6b580adcfa024ae48797ecdeb6825b4d"
dependencies = [
"libc",
"redox_users",
"winapi",
]
[[package]]
name = "either"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a26ae43d7bcc3b814de94796a5e736d4029efb0ee900c12e2d54c993ad1a1e07"
[[package]]
name = "enum-as-inner"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
version = "0.6.0"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "5ffccbb6966c05b32ef8fbac435df276c4ae4d3dc55a8cd0eb9745e6c12f546a"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
"heck",
"proc-macro2",
"quote",
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"syn 2.0.27",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
]
[[package]]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
name = "errno"
version = "0.3.2"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "6b30f669a7961ef1631673d2766cc92f52d64f7ef354d4fe0ddfd30ed52f0f4f"
dependencies = [
"errno-dragonfly",
"libc",
"windows-sys",
]
[[package]]
name = "errno-dragonfly"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa68f1b12764fab894d2755d2518754e71b4fd80ecfb822714a1206c2aab39bf"
dependencies = [
"cc",
"libc",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
[[package]]
name = "fuzzy-matcher"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54614a3312934d066701a80f20f15fa3b56d67ac7722b39eea5b4c9dd1d66c94"
dependencies = [
"thread_local",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "generic-array"
version = "0.14.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
dependencies = [
"typenum",
"version_check",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "getrandom"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.10"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "be4136b2a15dd319360be1c07d9933517ccf0be8f16bf62a3bee4f0d618df427"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cfg-if",
"libc",
"wasi 0.11.0+wasi-snapshot-preview1",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "gimli"
version = "0.27.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6c80984affa11d98d1b88b66ac8853f143217b399d3c74116778ff8fdb4ed2e"
[[package]]
name = "hashbrown"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
dependencies = [
"ahash",
]
[[package]]
name = "heck"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "95505c38b4572b2d910cecb0281560f54b440a19336cbbcb27bf6ce6adc6f5a8"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
[[package]]
name = "hermit-abi"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "0.3.2"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "443144c8cdadd93ebf52ddb4056d257f5b52c04d3c804e657d19eb73fc33668b"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "iana-time-zone"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.1.57"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "2fad5b825842d2b38bd206f3e81d6957625fd7f0a361e345c30e01a0ae2dd613"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"android_system_properties",
"core-foundation-sys",
"iana-time-zone-haiku",
"js-sys",
"wasm-bindgen",
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"windows",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "iana-time-zone-haiku"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.1.2"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"cc",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
name = "is-terminal"
version = "0.4.9"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "cb0889898416213fab133e1d33a0e5858a48177452750691bde3666d0fdbaf8b"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"hermit-abi",
"rustix",
"windows-sys",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
]
[[package]]
name = "itertools"
version = "0.10.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b0fd2260e829bddf4cb6ea802289de2f86d6a7a690192fbe91b3f46e0f2c8473"
dependencies = [
"either",
]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "itertools"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b1c173a5686ce8bfa551b3563d0c2170bf24ca44da99c7ca4bfdab5418c3fe57"
dependencies = [
"either",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "itoa"
version = "1.0.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "af150ab688ff2122fcef229be89cb50dd66af9e01a4ff320cc137eecc9bacc38"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "js-sys"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.3.64"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "c5f195fe497f702db0f318b07fdd68edb16955aed830df8363d837542f8f935a"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"wasm-bindgen",
]
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
[[package]]
name = "libc"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.147"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "b4668fb0ea861c1df094127ac5f1da3409a82116a4ba74fca2e58ef927159bb3"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "link-cplusplus"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.0.9"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "9d240c6f7e1ba3a28b0249f774e6a9dd0175054b52dfbb61b16eb8505c3785c9"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cc",
]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "linux-raw-sys"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "57bcfdad1b858c2db7c38303a6d2ad4dfaf5eb53dfeb0910128b2c26d6158503"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "log"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.4.19"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "b06a4cde4c0f271a446782e3eff8de789548ce57dbc8eca9292c27f4a42004b4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "memchr"
version = "2.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
[[package]]
name = "memoffset"
version = "0.6.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5aa361d4faea93603064a027415f07bd8e1d5c88c9fbf68bf56a285428fd79ce"
dependencies = [
"autocfg",
]
[[package]]
name = "memoffset"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.9.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "5a634b1c61a95585bd15607c6ab0c4e5b226e695ff2800ba0cdccddf208c406c"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"autocfg",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "minimal-lexical"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68354c5c6bd36d73ff3feceb05efa59b6acb7626617f4962be322a825e61f79a"
[[package]]
name = "miniz_oxide"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e7810e0be55b428ada41041c41f32c9f1a42817901b4ccf45fa3d4b6561e74c7"
dependencies = [
"adler",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "nix"
version = "0.24.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa52e972a9a719cecb6864fb88568781eb706bac2cd1d4f04a648542dbf78069"
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"bitflags 1.3.2",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"cfg-if",
"libc",
]
[[package]]
name = "nix"
version = "0.25.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f346ff70e7dbfd675fe90590b92d59ef2de15a8779ae305ebcbfd3f0caf59be4"
dependencies = [
"autocfg",
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"bitflags 1.3.2",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"cfg-if",
"libc",
"memoffset 0.6.5",
"pin-utils",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "nom"
version = "7.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d273983c5a657a70a3e8f2a01329822f3b8c8172b73826411a55751e404a0a4a"
dependencies = [
"memchr",
"minimal-lexical",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "num-traits"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "0.2.16"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "f30b0abd723be7e2ffca1272140fac1a2f084c77ec3e123c192b66af1ee9e6c2"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"autocfg",
]
[[package]]
name = "num_cpus"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.16.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "4161fcb6d602d4d2081af7c3a45852d875a03dd337a6bfdd6e06407b61342a43"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
"hermit-abi",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"libc",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "object"
version = "0.31.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8bda667d9f2b5051b8833f59f3bf748b28ef54f850f4fcb389a252aa383866d1"
dependencies = [
"memchr",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "once_cell"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.18.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "dd8b5dd2ae5ed71462c540258bedcb51965123ad7e7ccf4b9a8cafaa4a63576d"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
[[package]]
name = "proc-macro2"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.0.66"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "18fb31db3f9bddb2ea821cde30a9f70117e3f119938b5ee630b7403aa6e2ead9"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"unicode-ident",
]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "prql-ast"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "71194e75f14dbe7debdf2b5eca0812c978021a1bd23d6fe1da98b58e407e035a"
dependencies = [
"enum-as-inner",
"semver",
"serde",
"strum",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "prql-compiler"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
version = "0.9.3"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "5ff28e838b1be4227cc567a75c11caa3be25c5015f0e5fd21279c06e944ba44f"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"anstream",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"anyhow",
"ariadne",
"csv",
"enum-as-inner",
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"itertools 0.11.0",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"log",
"once_cell",
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"prql-ast",
"prql-parser",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"regex",
"semver",
"serde",
"serde_json",
"sqlformat",
"sqlparser",
"strum",
"strum_macros",
]
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "prql-parser"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3182e2ef0465a960eb02519b18768e39123d3c3a0037a2d2934055a3ef901870"
dependencies = [
"chumsky",
"itertools 0.11.0",
"prql-ast",
"semver",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "psm"
version = "0.1.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5787f7cda34e3033a72192c018bc5883100330f362ef279a8cbccfce8bb4e874"
dependencies = [
"cc",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "quote"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.0.31"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "5fe8a65d69dd0808184ebb5f836ab526bb259db23c657efa38711b1072ee47f0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"proc-macro2",
]
[[package]]
name = "rayon"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.7.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "1d2df5196e37bcc87abebc0053e20787d73847bb33134a69841207dd0a47f03b"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"either",
"rayon-core",
]
[[package]]
name = "rayon-core"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.11.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "4b8f95bd6966f5c87776639160a66bd8ab9895d9d4ab01ddba9fc60661aebe8d"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-utils",
"num_cpus",
]
[[package]]
name = "redox_syscall"
version = "0.2.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb5a58c1855b4b6819d59012155603f0b22ad30cad752600aadfcb695265519a"
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"bitflags 1.3.2",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "redox_users"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b033d837a7cf162d7993aded9304e30a83213c648b6e389db233191f891e5c2b"
dependencies = [
"getrandom",
"redox_syscall",
"thiserror",
]
[[package]]
name = "regex"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b2eae68fc220f7cf2532e4494aded17545fce192d59cd996e0fe7887f4ceb575"
dependencies = [
"aho-corasick",
"memchr",
"regex-automata",
"regex-syntax",
]
[[package]]
name = "regex-automata"
version = "0.3.3"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "39354c10dd07468c2e73926b23bb9c2caca74c5501e38a35da70406f1d923310"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax",
]
[[package]]
name = "regex-syntax"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "0.7.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "e5ea92a5b6195c6ef2a0295ea818b312502c6fc94dde986c5553242e18fd4ce2"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "rustc-demangle"
version = "0.1.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d626bb9dae77e28219937af045c257c28bfd3f69333c512553507f5f9798cb76"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
[[package]]
name = "rustix"
version = "0.38.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ee020b1716f0a80e2ace9b03441a749e402e86712f15f16fe8a8f75afac732f"
dependencies = [
"bitflags 2.3.3",
"errno",
"libc",
"linux-raw-sys",
"windows-sys",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "rustversion"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.0.14"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "7ffc183a10b4478d04cbbbfc96d0873219d962dd5accaff2ffbd4ceb7df837f4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "ryu"
version = "1.0.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ad4cc8da4ef723ed60bced201181d83791ad433213d8c24efffda1eec85d741"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "scopeguard"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.2.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "scratch"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.0.7"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "a3cf7c11c38cb994f3d40e8a8cde3bbd1f72a435e4c49e85d6553d8312306152"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "semver"
version = "1.0.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b0293b4b29daaf487284529cc2f5675b8e57c61f70167ba415a463651fd6a918"
dependencies = [
"serde",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "serde"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.174"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3b88756493a5bd5e5395d53baa70b194b05764ab85b59e43e4b8f4e1192fa9b1"
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_derive"
version = "1.0.174"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e5c3a298c7f978e53536f95a63bdc4c4a64550582f31a0359a9afda6aede62e"
dependencies = [
"proc-macro2",
"quote",
"syn 2.0.27",
]
[[package]]
name = "serde_json"
version = "1.0.103"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "d03b412469450d4404fe8499a268edd7f8b79fecb074b0d812ad64ca21f4031b"
dependencies = [
"itoa",
"ryu",
"serde",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "skim"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.10.4"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "e5d28de0a6cb2cdd83a076f1de9d965b973ae08b244df1aa70b432946dda0f32"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"beef",
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"bitflags 1.3.2",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"chrono",
"crossbeam",
"defer-drop",
"derive_builder",
"fuzzy-matcher",
"lazy_static",
"log",
"nix 0.25.1",
"rayon",
"regex",
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
"time 0.3.23",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"timer",
"tuikit",
"unicode-width",
"vte",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "sqlformat"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c12bc9199d1db8234678b7051747c07f517cdcf019262d1847b94ec8b1aee3e"
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"itertools 0.10.5",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"nom",
"unicode_categories",
]
[[package]]
name = "sqlparser"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
version = "0.36.1"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "2eaa1e88e78d2c2460d78b7dc3f0c08dbb606ab4222f9aff36f420d36e307d87"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
"log",
"serde",
]
[[package]]
name = "stacker"
version = "0.1.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c886bd4480155fd3ef527d45e9ac8dd7118a898a46530b7b94c3e21866259fce"
dependencies = [
"cc",
"cfg-if",
"libc",
"psm",
"winapi",
]
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "strum"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
version = "0.25.0"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "290d54ea6f91c969195bdbcd7442c8c2a2ba87da8bf60a7ee86a235d4bc1e125"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
"strum_macros",
]
[[package]]
name = "strum_macros"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
version = "0.25.1"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
checksum = "6069ca09d878a33f883cc06aaa9718ede171841d3832450354410b718b097232"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
dependencies = [
"heck",
"proc-macro2",
"quote",
"rustversion",
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"syn 2.0.27",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
]
[[package]]
name = "subtle"
version = "2.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "81cdd64d312baedb58e21336b31bc043b77e01cc99033ce76ef539f78e965ebc"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "syn"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.0.109"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
[[package]]
name = "syn"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "2.0.27"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "b60f673f44a8255b9c8c657daf66a596d435f2da81a555b06dc644d080ba45e0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
[[package]]
name = "term"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c59df8ac95d96ff9bede18eb7300b0fda5e5d8d90960e76f8e14ae765eedbf1f"
dependencies = [
"dirs-next",
"rustversion",
"winapi",
]
[[package]]
name = "termcolor"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.2.0"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "be55cf8942feac5c765c2c993422806843c9a9a45d4d5c407ad6dd2ea95eb9b6"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"winapi-util",
]
[[package]]
name = "thiserror"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.44"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "611040a08a0439f8248d1990b111c95baa9c704c805fa1f62104b39655fd7f90"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
version = "1.0.44"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
checksum = "090198534930841fab3a5d1bb637cde49e339654e606195f8d9c76eeb081dc96"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"proc-macro2",
"quote",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"syn 2.0.27",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
]
[[package]]
name = "thread_local"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "1.1.7"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "3fdd6f064ccff2d6567adcb3873ca630700f00b5ad3f060c25b5dcfd9a4ce152"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
"cfg-if",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"once_cell",
]
[[package]]
name = "time"
version = "0.1.45"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1b797afad3f312d1c66a56d11d0316f916356d11bd158fbc6ca6389ff6bf805a"
dependencies = [
"libc",
"wasi 0.10.0+wasi-snapshot-preview1",
"winapi",
]
[[package]]
name = "time"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "0.3.23"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "59e399c068f43a5d116fedaf73b203fa4f9c519f17e2b34f63221d3792f81446"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"serde",
"time-core",
]
[[package]]
name = "time-core"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.1.1"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "7300fbefb4dadc1af235a9cef3737cea692a9d97e1b9cbcd4ebdae6f8868e6fb"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "timer"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "31d42176308937165701f50638db1c31586f183f1aab416268216577aec7306b"
dependencies = [
"chrono",
]
[[package]]
name = "tuikit"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5e19c6ab038babee3d50c8c12ff8b910bdb2196f62278776422f50390d8e53d8"
dependencies = [
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
"bitflags 1.3.2",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"lazy_static",
"log",
"nix 0.24.3",
"term",
"unicode-width",
]
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "typenum"
version = "1.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "497961ef93d974e23eb6f433eb5fe1b7930b659f06d12dec6fc44a8f554c0bba"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "unicode-ident"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
version = "1.0.11"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Reduce dependencies for skim by avoid using default features By default skim requires cli -> clap -> termcolor -> winapi-util Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-19 10:29:39 +00:00
checksum = "301abaae475aa91687eb82514b328ab47a211a533026cb25fc3e519b86adfc3c"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "unicode-width"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0edd1e5b14653f783770bce4a4dabb4a5108a5370a5f5d8cfe8710c361f6c8b"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "unicode_categories"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "39ec24b3121d976906ece63c9daad25b85969647682eee313cb5779fdd69e14e"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "utf8parse"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.1"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "711b9620af191e0cdc7468a8d14e709c3dcdb115b36f838e601583af800a370a"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "version_check"
version = "0.9.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "vte"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.11.1"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "f5022b5fbf9407086c180e9557be968742d839e68346af7792b8592489732197"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"arrayvec",
"utf8parse",
"vte_generate_state_changes",
]
[[package]]
name = "vte_generate_state_changes"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d257817081c7dffcdbab24b9e62d2def62e2ff7d00b1c20062551e6cccc145ff"
dependencies = [
"proc-macro2",
"quote",
]
[[package]]
name = "wasi"
version = "0.10.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
[[package]]
name = "wasm-bindgen"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.87"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "7706a72ab36d8cb1f80ffbf0e071533974a60d0a308d01a5d0375bf60499a342"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"cfg-if",
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.87"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "5ef2b6d3c510e9625e5fe6f509ab07d66a760f0885d858736483c32ed7809abd"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"bumpalo",
"log",
"once_cell",
"proc-macro2",
"quote",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"syn 2.0.27",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-macro"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.87"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "dee495e55982a3bd48105a7b947fd2a9b4a8ae3010041b9e0faab3f9cd028f1d"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"quote",
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.87"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "54681b18a46765f095758388f2d0cf16eb8d4169b639ab575a8f5693af210c7b"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
dependencies = [
"proc-macro2",
"quote",
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
"syn 2.0.27",
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
version = "0.2.87"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
checksum = "ca6ad05a4870b2bf5fe995117d3728437bd27d7cd5f06f13c17443ef369775a1"
Integrate skim into the client/local Note, that it can the fail the client if the skim itself will fail, however I haven't seen it panicd, so let's try. P.S. about adding USE_SKIM into configure header instead of just compile option for target, it is better, because it allows not to recompile lots of C++ headers, since we have to add skim library as PUBLIC. But anyway this will be resolved in a different way, but separatelly. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-12-03 11:55:46 +00:00
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
"winapi",
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
[[package]]
name = "windows"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e686886bc078bc1b0b600cac0147aadb815089b6e4da64016cbd754b6342700f"
build: Upgrade PRQL version
2023-08-04 18:34:00 +00:00
dependencies = [
"windows-targets",
]
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
Run cargo update to fix build with nightly
2023-07-03 07:40:36 +00:00
dependencies = [
"windows-targets",
]
[[package]]
name = "windows-targets"
version = "0.48.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "05d4b17490f70499f20b9e791dcf6a299785ce8af4d709018206dc5b4953e95f"
dependencies = [
"windows_aarch64_gnullvm",
"windows_aarch64_msvc",
"windows_i686_gnu",
"windows_i686_msvc",
"windows_x86_64_gnu",
"windows_x86_64_gnullvm",
"windows_x86_64_msvc",
]
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "91ae572e1b79dba883e0d315474df7305d12f569b400fcf90581b06062f7e1bc"
[[package]]
name = "windows_aarch64_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b2ef27e0d7bdfcfc7b868b317c1d32c641a6fe4629c171b8928c7b08d98d7cf3"
[[package]]
name = "windows_i686_gnu"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "622a1962a7db830d6fd0a69683c80a18fda201879f0f447f065a3b7467daa241"
[[package]]
name = "windows_i686_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4542c6e364ce21bf45d69fdd2a8e455fa38d316158cfd43b3ac1c5b1b19f8e00"
[[package]]
name = "windows_x86_64_gnu"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca2b8a661f7628cbd23440e50b05d705db3686f894fc9580820623656af974b1"
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7896dbc1f41e08872e9d5e8f8baa8fdd2677f29468c4e156210174edc7f7b953"
[[package]]
name = "windows_x86_64_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a515f5799fe4961cb532f983ce2b23082366b898e52ffbce459c86f67c8378a"
Reproducible builds for Rust From now on cargo will not download anything from the internet during builds. This step had been moved for docker image builds (via cargo vendor). And now cargo inside docker.io/clickhouse/binary-builder will not use any crates from the internet, so we don't need to add --offline for cargo commands in cmake (corrosion_import_crate()). Also the docker build command had been adjusted to allow following symlinks inside build context, by using tar, this is required for Rust packages. Note, that to make proper Cargo.lock that could be vendored I did the following: - per-project locks had been removed (since there is no automatic way to sync the workspace Cargo.lock with per-project Cargo.lock, since cargo update/generate-lockfile will use only per-project Cargo.toml files apparently, -Z minimal-versions does not helps either) - and to generate Cargo.lock with less changes I've pinned version in the Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"' then the Cargo.lock for workspace had been generated and afterwards I've reverted this part. Plus I have to update the dependencies afterwards, since otherwise there are conflicts with dependencies for std library. Non trivial. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-07-21 06:31:45 +00:00
[[package]]
name = "yansi"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "09041cd90cf85f7f8b2df60c646f853b7f535ce68f85244eb6731cf89fa498ec"
Reference in New Issue Copy Permalink