hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2025-01-07 08:13:18 +03:00
Code Issues Projects Releases Wiki Activity
00e86292ac
graphql-engine/v3/crates/tracing-util/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

28 lines
603 B
TOML
Raw Normal View History

v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
[package]
name = "tracing-util"
Set the crate properties once, to improve the Nix build. (#334) V3_GIT_ORIGIN_REV_ID: ec5f3d968306a64ad5c63df324ca5c524838c598
2024-03-06 20:14:24 +03:00
version.workspace = true
edition.workspace = true
license.workspace = true
v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
Disable benchmarks in unit tests. (#376) This means that we can pass arguments to the Criterion benchmarks because the test binaries do not try and run. For example, if you run this: ``` cargo bench -- --warm-up-time=1 --measurement-time=1 ``` … it will currently fail, because it will also pass these arguments to the tests. Disabling the benchmarks for the tests fixes this. V3_GIT_ORIGIN_REV_ID: 10fe0683b82c506e1a11b24ca0a0a4041e37b655
2024-03-21 15:41:31 +03:00
[lib]
bench = false
v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
[dependencies]
derive_more = "0.99.17"
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
http = "0.2.9"
downgrade opentelemetry versions (#380) <!-- Thank you for submitting this PR! :) --> ## Description This PR downgrades the opentelemetry versions to 0.20. This fixed the tracing propagation issues faced [here](https://hasurahq.slack.com/archives/C066TKMH79R/p1710177836329809). ### TODOs: - [ ] Figure out the exact issue which caused the context propagation to stop working - [ ] Open an issue with [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust) (if required). Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0bc4d8142bd2f671e04d1cbf806f4626e2217332
2024-03-21 12:56:35 +03:00
# version > 0.20 of opentelemetry doesn't work well with our tracing-utils
opentelemetry = "0.20.0"
add exports to `tracing-util` (#387) <!-- Thank you for submitting this PR! :) --> ## Description We don't want `v3-engine-multitenant` to import any opentelemetry libraries directly, so we add more functions and re-exports here instead. V3_GIT_ORIGIN_REV_ID: 2e38b9b1ba6fda23d1bfe8e20549c3a95bd5a2fa
2024-03-25 12:48:24 +03:00
opentelemetry-contrib = "0.12.0"
downgrade opentelemetry versions (#380) <!-- Thank you for submitting this PR! :) --> ## Description This PR downgrades the opentelemetry versions to 0.20. This fixed the tracing propagation issues faced [here](https://hasurahq.slack.com/archives/C066TKMH79R/p1710177836329809). ### TODOs: - [ ] Figure out the exact issue which caused the context propagation to stop working - [ ] Open an issue with [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust) (if required). Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0bc4d8142bd2f671e04d1cbf806f4626e2217332
2024-03-21 12:56:35 +03:00
opentelemetry-http = "0.9.0"
opentelemetry-otlp = "0.13.0"
opentelemetry_sdk = { version = "0.20.0", features = ["rt-tokio"] }
opentelemetry-semantic-conventions = "0.12.0"
re-add axum and machete-ignore it to fix tests run with cargo test (#418) <!-- Thank you for submitting this PR! :) --> ## Description For some reason, `cargo test` fails because of missing types in doc comment code, but `cargo nextest run` in CI does not. Re-adding `axum` as a dep dependency to `tracing-util` fixes this. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: 518e6faf702895d9c434056a57c40c2db6f4b0a8
2024-03-28 14:28:05 +03:00
[dev-dependencies]
axum = "0.6"
[package.metadata.cargo-machete]
ignored = [
"axum", # used in doc examples
]
Reference in New Issue Copy Permalink