hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2025-01-05 14:27:59 +03:00
Code Issues Projects Releases Wiki Activity
03856be0e0
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.

32 lines
615 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"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
http = "0.2"
opentelemetry = "0.22.0"
opentelemetry-contrib = "0.14.0"
opentelemetry-http = "0.11.0"
opentelemetry-otlp = "0.15.0"
opentelemetry_sdk = { version = "0.22.1", features = ["rt-tokio"] }
opentelemetry-semantic-conventions = "0.14.0"
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
opentelemetry-zipkin = "0.20.0"
tracing-subscriber = "0.3.18"
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
]
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
[lints]
workspace = true
Reference in New Issue Copy Permalink