mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-16 09:51:59 +03:00
cc9cedc268
6 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Samir Talwar
|
3a1968317b |
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 |
||
|
Samir Talwar
|
748bb3abab |
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 |
||
|
Samir Talwar
|
aa11947067 |
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 |
||
Daniel Harvey
|
e3bd16b5db |
Revert Bump serde_with from 2.3.3 to 3.7.0 (#381)
Reverts hasura/v3-engine#367 This is causing downstream problems in `v3-metadata-build-service`, let's roll back for now to unblock things. V3_GIT_ORIGIN_REV_ID: 3261f2f12825c8eac3353a2282b982f0f3bac80e |
||
dependabot[bot]
|
92fc015fac |
Bump serde_with from 2.3.3 to 3.7.0 (#367)
Bumps [serde_with](https://github.com/jonasbb/serde_with) from 2.3.3 to 3.7.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jonasbb/serde_with/releases">serde_with's releases</a>.</em></p> <blockquote> <h2>serde_with v3.7.0</h2> <h3>Added</h3> <ul> <li>Implement <code>JsonSchemaAs</code> for <code>EnumMap</code> by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/697">#697</a>)</li> <li>Implement <code>JsonSchemaAs</code> for <code>IfIsHumanReadable</code> by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/717">#717</a>)</li> <li>Implement <code>JsonSchemaAs</code> for <code>KeyValueMap</code> by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/713">#713</a>)</li> <li>Implement <code>JsonSchemaAs</code> for <code>OneOrMany</code> by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/719">#719</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>Detect conflicting <code>schema_with</code> attributes on fields with <code>schemars</code> annotations by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/715">#715</a>) This extends the existing avoidance mechanism to a new variant fixing <a href="https://redirect.github.com/jonasbb/serde_with/issues/712">#712</a>.</li> </ul> <h2>serde_with v3.6.1</h2> <h3>Changed</h3> <ul> <li>Eliminate dependency on serde's "derive" feature by <a href="https://github.com/dtolnay"><code>@dtolnay</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/694">#694</a>) This allows parallel compilation of <code>serde</code> and <code>serde_derive</code> which can speed up the wallclock time. It requires that downstream crates do not use the "derive" feature either.</li> </ul> <h2>serde_with v3.6.0</h2> <h3>Added</h3> <ul> <li>Add <code>IfIsHumanReadable</code> for conditional implementation by <a href="https://github.com/irriden"><code>@irriden</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/690">#690</a>) Used to specify different transformations for text-based and binary formats.</li> <li>Add more <code>JsonSchemaAs</code> impls for all <code>Duration*</code> and <code>Timestamp*</code> adaptors by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/685">#685</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Bump MSRV to 1.65, since that is required for the <code>regex</code> dependency.</li> </ul> <h2>serde_with v3.5.1</h2> <h3>Fixed</h3> <ul> <li>The <code>serde_as</code> macro now better detects existing <code>schemars</code> attributes on fields and incorporates them by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/682">#682</a>) This avoids errors on existing <code>#[schemars(with = ...)]</code> annotations.</li> </ul> <h2>serde_with v3.5.0</h2> <h3>Added</h3> <ul> <li>Support for <code>schemars</code> integration added by <a href="https://github.com/swlynch99"><code>@swlynch99</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/666">#666</a>) The support uses a new <code>Schema</code> top-level item which implements <code>JsonSchema</code> The <code>serde_as</code> macro can now detect <code>schemars</code> usage and emits matching annotations for all fields with <code>serde_as</code> attribute. Many types of this crate come already with support for the <code>schemars</code>, but support is not complete and will be extended over time.</li> </ul> <h2>serde_with v3.4.0</h2> <ul> <li> <p>Lower minimum required serde version to 1.0.152 (<a href="https://redirect.github.com/jonasbb/serde_with/issues/653">#653</a>) Thanks to <a href="https://github.com/banool"><code>@banool</code></a> for submitting the PR.</p> <p>This allows people that have a problem with 1.0.153 to still use <code>serde_with</code>.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
Daniel Harvey
|
bdd5d06437 |
Move all crates into a folder (#355)
<!-- Thank you for submitting this PR! :) --> ## Description This moves all the crates into a `/crates` folder. Everything appears to just work, thanks Cargo! V3_GIT_ORIGIN_REV_ID: 8e3ef287b1a46cabdb4d919a50e813ab2cddf8b1 |