mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-16 01:44:03 +03:00
21c430ce8d
874 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
dependabot[bot]
|
21c430ce8d |
Bump serde from 1.0.214 to 1.0.215 (#1352)
Bumps [serde](https://github.com/serde-rs/serde) from 1.0.214 to 1.0.215. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.215</h2> <ul> <li>Produce warning when multiple fields or variants have the same deserialization name (<a href="https://redirect.github.com/serde-rs/serde/issues/2855">#2855</a>, <a href="https://redirect.github.com/serde-rs/serde/issues/2856">#2856</a>, <a href="https://redirect.github.com/serde-rs/serde/issues/2857">#2857</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
b3034e9c4f |
Bump axum from 0.7.7 to 0.7.9 (#1351)
Bumps [axum](https://github.com/tokio-rs/axum) from 0.7.7 to 0.7.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/axum/releases">axum's releases</a>.</em></p> <blockquote> <h2>axum - v0.7.9</h2> <ul> <li><strong>fixed:</strong> Avoid setting content-length before middleware (<a href="https://redirect.github.com/tokio-rs/axum/issues/3031">#3031</a>)</li> </ul> <p><a href="https://redirect.github.com/tokio-rs/axum/issues/3031">#3031</a>:<a href="https://redirect.github.com/tokio-rs/axum/pull/3031">tokio-rs/axum#3031</a></p> <h2>axum - v0.7.8</h2> <ul> <li><strong>fixed:</strong> Skip SSE incompatible chars of <code>serde_json::RawValue</code> in <code>Event::json_data</code> (<a href="https://redirect.github.com/tokio-rs/axum/issues/2992">#2992</a>)</li> <li><strong>added:</strong> Add <code>method_not_allowed_fallback</code> to set a fallback when a path matches but there is no handler for the given HTTP method (<a href="https://redirect.github.com/tokio-rs/axum/issues/2903">#2903</a>)</li> <li><strong>added:</strong> Add <code>MethodFilter::CONNECT</code>, <code>routing::connect[_service]</code> and <code>MethodRouter::connect[_service]</code> (<a href="https://redirect.github.com/tokio-rs/axum/issues/2961">#2961</a>)</li> <li><strong>added:</strong> Add <code>NoContent</code> as a self-described shortcut for <code>StatusCode::NO_CONTENT</code> (<a href="https://redirect.github.com/tokio-rs/axum/issues/2978">#2978</a>)</li> </ul> <p><a href="https://redirect.github.com/tokio-rs/axum/issues/2903">#2903</a>: <a href="https://redirect.github.com/tokio-rs/axum/pull/2903">tokio-rs/axum#2903</a> <a href="https://redirect.github.com/tokio-rs/axum/issues/2961">#2961</a>: <a href="https://redirect.github.com/tokio-rs/axum/pull/2961">tokio-rs/axum#2961</a> <a href="https://redirect.github.com/tokio-rs/axum/issues/2978">#2978</a>: <a href="https://redirect.github.com/tokio-rs/axum/pull/2978">tokio-rs/axum#2978</a> <a href="https://redirect.github.com/tokio-rs/axum/issues/2992">#2992</a>: <a href="https://redirect.github.com/tokio-rs/axum/pull/2992">tokio-rs/axum#2992</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
6b40ae4c14 |
Bump tokio from 1.41.0 to 1.41.1 (#1350)
Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.41.0 to 1.41.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tokio/releases">tokio's releases</a>.</em></p> <blockquote> <h2>Tokio v1.41.1</h2> <h1>1.41.1 (Nov 7th, 2024)</h1> <h3>Fixed</h3> <ul> <li>metrics: fix bug with wrong number of buckets for the histogram (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6957">#6957</a>)</li> <li>net: display <code>net</code> requirement for <code>net::UdpSocket</code> in docs (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6938">#6938</a>)</li> <li>net: fix typo in <code>TcpStream</code> internal comment (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6944">#6944</a>)</li> </ul> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6957">#6957</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6957">tokio-rs/tokio#6957</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6938">#6938</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6938">tokio-rs/tokio#6938</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6944">#6944</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6944">tokio-rs/tokio#6944</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
Daniel Harvey
|
bf61f3e18b |
Use type rather than model names in JSONAPI sparse fields (#1349)
<!-- The PR description should answer 2 important questions: --> ### What Given a model name `Authors` with an `Author` type underneath, this changes field selection for JSONAPI to use `fields[Author]` instead of `fields[Authors]`. This will make things more consistent when we are also filtering other types from relationships or nested fields too, which will have to use type names, for example `fields[Author]=name,articles&fields[Article]=title` V3_GIT_ORIGIN_REV_ID: fff43c673888877ca8b2edb6e5ca9fdc846675a5 |
||
|
Daniel Harvey
|
ee3c1a5a9a |
Make using ObjectBooleanExpressionType an error (#1344)
<!-- The PR description should answer 2 important questions: --> ### What These have been deprecated for a while, and we now have a codemod to fix users metadata, so it's time to make these officially deprecated. Any `ObjectBooleanExpressionType` will now raise an error. V3_GIT_ORIGIN_REV_ID: f3dd18afba40e369e82a15a7fbbfe31004d44067 |
||
|
Daniel Harvey
|
4e89dd40eb |
Use BooleanExpressionType in new plan filtering (#1334)
<!-- The PR description should answer 2 important questions: --> ### What Previously the OpenDD pipeline has ignored `BooleanExpressionType` as they were not available outside GraphQL. Now they are, so we use them, and test them in the JSONAPI pipeline. This means that the SQL frontend cannot use filtering unless models have a `BooleanExpressionType` defined. These are generated by the CLI, so hopefully this is fine. Depends on #1336 V3_GIT_ORIGIN_REV_ID: 4037585ef36bc99c99a482361084ccd09c5c6bb1 |
||
|
Daniel Harvey
|
6e69ae03c3 |
Remove misleading JSONB from Order By changelog entry (#1347)
<!-- The PR description should answer 2 important questions: --> ### What What's important about the feature is that it accesses nested fields rather than being specific to any particular underlying representation. V3_GIT_ORIGIN_REV_ID: 648464f925f23efde2e764b709a9b3e067ff6a57 |
||
|
Daniel Harvey
|
3cb1fc67f6 |
Add metrics for JSONAPI (#1345)
V3_GIT_ORIGIN_REV_ID: a2a0c4ba404dce98c851c8637917219fc5b2d625 |
||
Daniel Chambers
|
f255b5e48a |
Nested relationships: Refactor capabilities, add engine test, fix docker compose engine metadata (#1341)
### What This PR does three related things: * Adds an execution test that tests that nested relationships work in field selection in Postgres (taken from #935) * Refactors the way capabilities are handled in metadata resolve to account for difference between NDC 0.1.x and 0.2.x. Specifically, NDC 0.1.x connectors are assumed to support nested relationships in field selection, but do not support them in filtering and ordering. Whereas in NDC 0.2.x, a capability exists to indicate nested relationship support, but then you must support them in filtering and ordering as well as field selection. * Updates the metadata used in the default docker compose so that it: * uses an up to date pg schema * uses BooleanExpressionType instead of ObjectBooleanExpression * removes commands that do not exist on the pg connector * adds the Institutions model so that nested relationships can be tested This PR does not add support for nested relationships in filtering or in ordering. It also does not block nested relationships in field selection for NDC 0.2.x connectors that do not support it. This will all come in later PRs. ### How In `metadata_resolve`, the resolved `DataConnector` used to contain a copy of the `ndc_models::Capabilities`. This has been removed and instead a `metadata_resolve` specific `DataConnectorCapabilities` structure is used instead. This decouples `metadata_resolve` from `ndc_models` and allows it to capture differences between NDC 0.1.x and 0.2.x properly. There is now a specific function per NDC version that creates a `DataConnectorCapabilities`. This removes the need for capabilities migration code. V3_GIT_ORIGIN_REV_ID: 0eb119aab0e5fa22977d84820025f75c6102036d |
||
|
Daniel Harvey
|
dd070be7fb |
Changelog for v2024.11.13 (#1343)
<!-- The PR description should answer 2 important questions: --> ### What Update changelog for `v2024.11.13` V3_GIT_ORIGIN_REV_ID: e8ef1db536825e8266c663978be6832463e8d378 |
||
paritosh-08
|
104365205c |
wip: plan refactor type changes (part 1) (#1339)
--------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: c1b88c89d2ad9ad80e20a1763f036db85798ec3b |
||
|
Daniel Harvey
|
85afd13f34 |
OperatorMapping struct newtype (#1336)
<!-- The PR description should answer 2 important questions: --> ### What Operator mappings in boolean expressions allow us to override the name of an operator, so we can call some database's `_eq` operator the much more attractive `equals`. If not override is provided we can just use the database's name directly. We make this a newtype with a `get` function to encode this logic and make doing the right thing the easiest thing. V3_GIT_ORIGIN_REV_ID: e47f4e291494562ed1551d0d7469259198862a0a |
||
|
Daniel Harvey
|
a2353ae3de |
Revert "Build: use native target CPU (#1330)" (#1338)
This reverts commit 7b5d5668b3a8949dd56b2a887f10d964d523bdd6. <!-- The PR description should answer 2 important questions: --> ### What Deployed different commits to `staging` and this one broke it, so rolling it back. V3_GIT_ORIGIN_REV_ID: ba93bbc61b38d2c756e109e24566f8d51b01d458 |
||
Rakesh Emmadi
|
c780aaed53 |
graphql-ws: send keepalive messages to the client at regular intervals (#1335)
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Send `type: ping` messages on a websocket connection at regular intervals to avoid keeping it idle. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> - Spawn an async thread that send the ping messages at regular intervals. - Abort the thread before closing a connection. A test case is written to confirm the keepalive messsage sent. Also this PR does a tiny no-op refactor to the `expect_text_message` helper function in the graphql-ws tests. V3_GIT_ORIGIN_REV_ID: 65b02cf1f6502bd3a6a9460673e3d87f24738d33 |
||
|
Daniel Harvey
|
41c9b1d816 |
Changelog for v2024.11.11 (#1333)
<!-- The PR description should answer 2 important questions: --> ### What Updated changelog for release `v2024.11.11` V3_GIT_ORIGIN_REV_ID: 4ced0b477a8b147e53e7516512abbc4de2384ab7 |
||
|
Rakesh Emmadi
|
716b50fbb8 |
set the request.type = http | websocket attribute in the opening spans (#1332)
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Set the `request.type` attribute in the opening spans to determine the request type, either http or websocket. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> Define an enum type to capture the request type and set its `to_str()` value in the `request.type` attribute. V3_GIT_ORIGIN_REV_ID: d0370d8a5b7938a546a74641bf7bfee6da2dd33f |
||
|
Rakesh Emmadi
|
bbdedbb258 |
metadata-resolve: disallow duplicate model root fields (#1322)
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Disallow duplicate root fields in a model GraphQL config. This is a backward incompatible change which could break any existing builds with duplicate root fields. Hence, this check is guarded behind a compatibility date. However, warnings are thrown during a build if metadata contains duplicate graphql root fields. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> Add a check while resolving the graphql metadata of a model definition. V3_GIT_ORIGIN_REV_ID: d083c62fa359df8742bbc16df821d46275d29e79 |
||
|
dependabot[bot]
|
5c5af7e8da |
Bump url from 2.5.2 to 2.5.3 (#1325)
Bumps [url](https://github.com/servo/rust-url) from 2.5.2 to 2.5.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/servo/rust-url/releases">url's releases</a>.</em></p> <blockquote> <h2>v2.5.3</h2> <h2>What's Changed</h2> <ul> <li>fix: enable wasip2 feature for wasm32-wasip2 target by <a href="https://github.com/brooksmtownsend"><code>@brooksmtownsend</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/960">servo/rust-url#960</a></li> <li>Fix idna tests with no_std by <a href="https://github.com/cjwatson"><code>@cjwatson</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/963">servo/rust-url#963</a></li> <li>Fix debugger_visualizer test failures. by <a href="https://github.com/valenting"><code>@valenting</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/967">servo/rust-url#967</a></li> <li>Add AsciiSet::EMPTY and boolean operators by <a href="https://github.com/joshka"><code>@joshka</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/969">servo/rust-url#969</a></li> <li>mention why we pin unicode-width by <a href="https://github.com/Manishearth"><code>@Manishearth</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/972">servo/rust-url#972</a></li> <li>refactor and add tests for percent encoding by <a href="https://github.com/joshka"><code>@joshka</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/977">servo/rust-url#977</a></li> <li>Add a test for and fix issue <a href="https://redirect.github.com/servo/rust-url/issues/974">#974</a> by <a href="https://github.com/hansl"><code>@hansl</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/975">servo/rust-url#975</a></li> <li><code>no_std</code> support for the <code>url</code> crate by <a href="https://github.com/domenukk"><code>@domenukk</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/831">servo/rust-url#831</a></li> <li>Normalize URL paths: convert /.//p, /..//p, and //p to p by <a href="https://github.com/theskim"><code>@theskim</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/943">servo/rust-url#943</a></li> <li>support Hermit by <a href="https://github.com/m-mueller678"><code>@m-mueller678</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/985">servo/rust-url#985</a></li> <li>fix: support <code>wasm32-wasip2</code> on the stable channel by <a href="https://github.com/brooksmtownsend"><code>@brooksmtownsend</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/983">servo/rust-url#983</a></li> <li>Improve serde error output by <a href="https://github.com/konstin"><code>@konstin</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/982">servo/rust-url#982</a></li> <li>OSS-Fuzz: Add more fuzzer by <a href="https://github.com/arthurscchan"><code>@arthurscchan</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/988">servo/rust-url#988</a></li> <li>Merge idna-v1x to main by <a href="https://github.com/hsivonen"><code>@hsivonen</code></a> in <a href="https://redirect.github.com/servo/rust-url/pull/990">servo/rust-url#990</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/brooksmtownsend"><code>@brooksmtownsend</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/960">servo/rust-url#960</a></li> <li><a href="https://github.com/cjwatson"><code>@cjwatson</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/963">servo/rust-url#963</a></li> <li><a href="https://github.com/joshka"><code>@joshka</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/969">servo/rust-url#969</a></li> <li><a href="https://github.com/hansl"><code>@hansl</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/975">servo/rust-url#975</a></li> <li><a href="https://github.com/theskim"><code>@theskim</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/943">servo/rust-url#943</a></li> <li><a href="https://github.com/m-mueller678"><code>@m-mueller678</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/985">servo/rust-url#985</a></li> <li><a href="https://github.com/konstin"><code>@konstin</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/982">servo/rust-url#982</a></li> <li><a href="https://github.com/arthurscchan"><code>@arthurscchan</code></a> made their first contribution in <a href="https://redirect.github.com/servo/rust-url/pull/988">servo/rust-url#988</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/servo/rust-url/compare/v2.5.2...v2.5.3">https://github.com/servo/rust-url/compare/v2.5.2...v2.5.3</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
Daniel Harvey
|
056b1c18fc |
Stop Nix rebuilding (#1329)
<!-- The PR description should answer 2 important questions: --> ### What Our Nix build was building all the workspace crates as part of it's deps step. This means when any library crate is changed, we throw away all the caching, which isn't ideal. This filters the source files out of those builds, so that we get more cache hits. We also move all Cargo features into the workspace, which I've been meaning to do for ages, so things are more consistent, and again, we get more cache hits generally. V3_GIT_ORIGIN_REV_ID: c724b152692575edf6c00ab426e48ecca13aa998 |
||
|
Daniel Harvey
|
9f28f41a0e |
Build: use native target CPU (#1330)
<!-- The PR description should answer 2 important questions: --> ### What Have seen this advised in both the [Rust Performance Book](https://nnethercote.github.io/perf-book/build-configuration.html#cpu-specific-instructions) and in the [Datafusion docs](https://datafusion.apache.org/user-guide/crate-configuration.html), seems like there's no drawbacks and the possibility of extra juice. My M1 Mac shows a no-op in benchmarks, but since it's going to change depending on CPU plan to merge and take a look at the CI benchmarks too. V3_GIT_ORIGIN_REV_ID: 7b5d5668b3a8949dd56b2a887f10d964d523bdd6 |
||
|
Daniel Harvey
|
41fb74faba |
Move boolean expression fields out of graphql config (#1319)
<!-- The PR description should answer 2 important questions: --> ### What We only resolve boolean expression fields if there is a `graphql` name defined, which is not helpful for using them in JSONAPI or SQL. This makes the validation happen earlier. This means users that have broken boolean expressions that did not have a `graphql` field would have been allowed to sit broken, but now those will error, so this is behind a new compatibility config flag. ### How Move `scalar_fields` and `object_fields` resolve into `object` steps instead of the `graphql` steps of resolve for `ObjectBooleanExpressionType` and `BooleanExpressionType`. Note: we really need to get `ObjectBooleanExpressionType` deprecated and deleted, it causes so much extra work and complexity everywhere. V3_GIT_ORIGIN_REV_ID: c6f0849d412b40f3484fb44c1b36ebdf77ac60c1 |
||
|
dependabot[bot]
|
cfda861bdc |
Bump serde from 1.0.210 to 1.0.214 (#1327)
Bumps [serde](https://github.com/serde-rs/serde) from 1.0.210 to 1.0.214. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.214</h2> <ul> <li>Implement IntoDeserializer for all Deserializers in serde:🇩🇪:value module (<a href="https://redirect.github.com/serde-rs/serde/issues/2568">#2568</a>, thanks <a href="https://github.com/Mingun"><code>@Mingun</code></a>)</li> </ul> <h2>v1.0.213</h2> <ul> <li>Fix support for macro-generated <code>with</code> attributes inside a newtype struct (<a href="https://redirect.github.com/serde-rs/serde/issues/2847">#2847</a>)</li> </ul> <h2>v1.0.212</h2> <ul> <li>Fix hygiene of macro-generated local variable accesses in serde(with) wrappers (<a href="https://redirect.github.com/serde-rs/serde/issues/2845">#2845</a>)</li> </ul> <h2>v1.0.211</h2> <ul> <li>Improve error reporting about mismatched signature in <code>with</code> and <code>default</code> attributes (<a href="https://redirect.github.com/serde-rs/serde/issues/2558">#2558</a>, thanks <a href="https://github.com/Mingun"><code>@Mingun</code></a>)</li> <li>Show variant aliases in error message when variant deserialization fails (<a href="https://redirect.github.com/serde-rs/serde/issues/2566">#2566</a>, thanks <a href="https://github.com/Mingun"><code>@Mingun</code></a>)</li> <li>Improve binary size of untagged enum and internally tagged enum deserialization by about 12% (<a href="https://redirect.github.com/serde-rs/serde/issues/2821">#2821</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
9b86af2486 |
Bump csv from 1.3.0 to 1.3.1 (#1326)
Bumps [csv](https://github.com/BurntSushi/rust-csv) from 1.3.0 to 1.3.1. <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
13043ccd3e |
Bump thiserror from 1.0.64 to 1.0.69 (#1324)
Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.64 to 1.0.69. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/thiserror/releases">thiserror's releases</a>.</em></p> <blockquote> <h2>1.0.69</h2> <ul> <li>Backport 2.0.2 fixes</li> </ul> <h2>1.0.68</h2> <ul> <li>Handle incomplete expressions more robustly in format arguments, such as while code is being typed (<a href="https://redirect.github.com/dtolnay/thiserror/issues/341">#341</a>, <a href="https://redirect.github.com/dtolnay/thiserror/issues/344">#344</a>)</li> </ul> <h2>1.0.67</h2> <ul> <li>Improve expression syntax support inside format arguments (<a href="https://redirect.github.com/dtolnay/thiserror/issues/335">#335</a>, <a href="https://redirect.github.com/dtolnay/thiserror/issues/337">#337</a>, <a href="https://redirect.github.com/dtolnay/thiserror/issues/339">#339</a>, <a href="https://redirect.github.com/dtolnay/thiserror/issues/340">#340</a>)</li> </ul> <h2>1.0.66</h2> <ul> <li>Improve compile error on malformed format attribute (<a href="https://redirect.github.com/dtolnay/thiserror/issues/327">#327</a>)</li> </ul> <h2>1.0.65</h2> <ul> <li>Ensure OUT_DIR is left with deterministic contents after build script execution (<a href="https://redirect.github.com/dtolnay/thiserror/issues/325">#325</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
Brandon Simmons
|
efee881784 |
ENG-1227: mbs: reduce artifact size by omitting "default" values (#1323)
We get a 17% reduction in size for chinook.json, 14% for our big schema. Benchmark is 8% faster for chinook.json <!-- The PR description should answer 2 important questions: --> ### What reduce artifact size ### How remove certain common "default" fields on serialization, to be repopulated on deserialization. Since this works at the serde level we should still benefit if we manage to switch to e.g. bincode I attempted to create a macro for this, but decided it wasn't worth it. Fields were chosen by sorting and counting json fields, and adding these annotations for the heaviest ones. V3_GIT_ORIGIN_REV_ID: 4605016021fa6aafb97759e3bd5346116413a0ef |
||
|
Rakesh Emmadi
|
91f74550b5 |
metadata-resolve: refactor duplicate root field reporting in commands (#1320)
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> No-op refactor. Just updates the error message. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> Define a type to track root fields and report error if the field is already in use. V3_GIT_ORIGIN_REV_ID: 91533ee0dd48087617e1950f1aeb42a1787edc16 |
||
|
Daniel Chambers
|
d3491fc9f6 |
Upgrade to NDC v0.2.0-rc.1 (#1291)
### What This PR updates the engine to use the NDC Spec v0.2.0-rc.1 version. This is very likely to be the final RC before release. ### How The `ndc_models` crate got updated, which then resulted in the schema migration code in `metadata_resolve` being updated. This affected a lot of test results because connectors that used deprecated type representations got migrated to other representations, and if a type representation was missing then JSON was used instead. The NDC request-sending code in `execute` was updated to send the `X-Hasura-NDC-Version` header depending on the version of request getting sent. The custom connector was updated to be compatible with the new NDC 0.2.0-rc.1 types. This resulted in the schema changing, so a lot of tests that contained the connector's schema were updated. --------- Co-authored-by: Daniel Harvey <danieljamesharvey@gmail.com> V3_GIT_ORIGIN_REV_ID: b1c7081eb1ee6cffdead08328a857903102332c6 |
||
|
Daniel Harvey
|
82489ad32f |
Update type representations (#1305)
<!-- The PR description should answer 2 important questions: --> ### What These are no longer used since https://github.com/hasura/v3-engine/pull/1301, let's remove them from the metadata. V3_GIT_ORIGIN_REV_ID: 17194f7fa30860738e99de6098fa84d212fee0d2 |
||
|
Daniel Harvey
|
9790e1fd86 |
JSONAPI filtering part 1 (#1314)
<!-- The PR description should answer 2 important questions: --> ### What First iteration of JSONAPI filtering What does it do? - Field comparisons against values - And - Or What doesn't it do - Generate schema - Use `BooleanExpressionType` to work out which operators are available - Work for nested fields (which don't work anyway atm) V3_GIT_ORIGIN_REV_ID: 71f490b2767275b5e57fa4bcf213f2339391c093 |
||
|
Daniel Harvey
|
c62e5fed32 |
Enable strictDeps in our Nix builds (#1318)
<!-- The PR description should answer 2 important questions: --> ### What All the docs examples have it, [it's recommended by the author](https://github.com/ipetkov/crane/issues/403#issuecomment-1743416192), and it should help with unnecessary rebuilds. V3_GIT_ORIGIN_REV_ID: 3596dd987090756e0914f7babb1329c0d9c1a263 |
||
|
Daniel Harvey
|
9f7d961209 |
Update changelog for v2024.11.05 (#1317)
<!-- The PR description should answer 2 important questions: --> ### What Changelog update. V3_GIT_ORIGIN_REV_ID: 3162167208fd9cce1d5f5bda4f28ef3f65339ce9 |
||
|
Daniel Harvey
|
1b143c10ff |
Fix JSONAPI sparse fields (#1316)
<!-- The PR description should answer 2 important questions: --> ### What Accidentally made the fallthrough to show all fields too liberal, so our "include this field?" function became const true. Now we check properly. V3_GIT_ORIGIN_REV_ID: a56ce76e1cdf57ea17856b9835128f75b3cf18c3 |
||
|
Rakesh Emmadi
|
d4465ce035 |
graphql-ws: fix stop all pollers when a connection is dropped (#1315)
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Fix a bug with pollers are not being stopped when the connection is dropped. ### How Fetch all poller operation ids at once from a mutex map and stop each poller associated with them in a for-loop. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: f17511d611b92ace3de2c83e606d26214649878b |
||
|
Daniel Harvey
|
c8d43adb1c |
JSONAPI in multitenant (#1303)
V3_GIT_ORIGIN_REV_ID: 9be48c7e0fa948a1c36d94a48f0a2913984b24a7 |
||
|
Daniel Harvey
|
df79ec144c |
Print nix build debugging in build (#1313)
<!-- The PR description should answer 2 important questions: --> ### What I feel like Nix builds more than it should, and I'm interested why. [According to the crane docs](https://crane.dev/faq/constant-rebuilds.html#debugging-with-just-nix), we can use this to hopefully see what is going on, by diffing the output between builds. ### How Add `nix derivation show -r .#output` as a build step. V3_GIT_ORIGIN_REV_ID: 32bce8315874b9effb075aa834a891cf0dcc00e2 |
||
|
Daniel Harvey
|
e537c88d4f |
Use BTreeSet to collect Role in metadata-resolve (#1312)
<!-- The PR description should answer 2 important questions: --> ### What JSONAPI builds iterate over `roles` in metadata, and one was very slow, realised it was because it was calculating for `admin` over and over. This changes the `roles` in `metadata-resolve` to be collected in a `BTreeSet` to remove duplicates, which fixes the problem. ### How Change `Vec` to `BTreeSet`, fix type errors and snapshots. V3_GIT_ORIGIN_REV_ID: c61ef9e490c3cde9d004c08ef71dc73e92cd6e7e |
||
|
dependabot[bot]
|
1667c96c5d |
Bump derive_more from 0.99.18 to 1.0.0 (#1310)
Bumps [derive_more](https://github.com/JelteF/derive_more) from 0.99.18 to 1.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/JelteF/derive_more/releases">derive_more's releases</a>.</em></p> <blockquote> <h2>v1.0.0 - Finally a stable release</h2> <p><code>derive_more</code> is a library that adds derives for many of the standard library traits. By using this library the following code just works:</p> <pre lang="rust"><code>use derive_more::{Add, Display, From, Into}; <p>#[derive(PartialEq, From, Add)] struct MyInt(i32);</p> <p>#[derive(PartialEq, From, Into)] struct Point2D { x: i32, y: i32, }</p> <p>#[derive(PartialEq, From, Add, Display)] enum MyEnum { #[display("int: {_0}")] Int(i32), Uint(u32), #[display("nothing")] Nothing, }</p> <p>assert!(MyInt(11) == MyInt(5) + 6.into()); assert!((5, 6) == Point2D { x: 5, y: 6 }.into()); assert!(MyEnum::Int(15) == (MyEnum::Int(8) + 7.into()).unwrap()); assert!(MyEnum::Int(15).to_string() == "int: 15"); assert!(MyEnum::Uint(42).to_string() == "42"); assert!(MyEnum::Nothing.to_string() == "nothing"); </code></pre></p> <p>Now, more than 8 years after the first commit and almost 5 years after the 0.99.0 release, <code>derive_more</code> has finally reached its 1.0.0 release. This release contains a lot of changes (including some breaking ones) to make it easier to use the derives and make it possible to extend them without having to break backwards compatibility again. There are five major changes that I would like to call out, but there are many more changes that are documented below:</p> <ol> <li>There is a new <code>Debug</code> derive that can be used to easily customize <code>Debug</code> formatting.</li> <li>A greatly improved <code>Display</code> derive, which allows you to do anything that <a href="https://github.com/dtolnay/thiserror"><code>thiserror</code></a> provides, but it works for any type not just errors. And by combining the <code>Display</code> derive with the <code>Error</code> and <code>From</code> derives, there shouldn't really be any need to use <code>thiserror</code> anymore (if you are missing a feature/behaviour from <code>thiserror</code> please report an issue).</li> <li>Traits that can return errors now return a type that implements <code>Error</code> when an error occurs instead of a <code>&'static str</code>.</li> <li>When using <code>use derive_more::SomeTrait</code> the actual trait is also imported not just the derive macro. This is especially useful for <code>Error</code> and <code>Display</code></li> <li>The docs are now rendered on docs.rs and are much better overall.</li> </ol> <h3>Breaking changes</h3> <ul> <li>The minimum supported Rust version (MSRV) is now Rust 1.75.</li> <li>Add the <code>std</code> feature which should be disabled in <code>no_std</code> environments.</li> <li>All Cargo features, except <code>std</code>, are now disabled by default. The <code>full</code> feature can be used to get the old behavior of supporting all possible derives.</li> <li>The <code>TryFrom</code>, <code>Add</code>, <code>Sub</code>, <code>BitAnd</code>, <code>BitOr</code>, <code>BitXor</code>, <code>Not</code> and <code>Neg</code> derives now return a dedicated error type instead of a <code>&'static str</code> on error.</li> <li>The <code>FromStr</code> derive now uses a dedicated <code>FromStrError</code> error type instead of generating unique one each time.</li> <li>The <code>Display</code> derive (and other <code>fmt</code>-like ones) now uses <code>#[display("...", (<expr>),*)]</code> syntax instead of <code>#[display(fmt = "...", ("<expr>"),*)]</code>, and <code>#[display(bound(<bound>))]</code> instead of <code>#[display(bound = "<bound>")]</code>. So without the double quotes around the expressions and bounds.</li> <li>The <code>Debug</code> and <code>Display</code> derives (and other <code>fmt</code>-like ones) now transparently delegate to the inner type when <code>#[display("...", (<expr>),*)]</code> attribute is trivially substitutable with a transparent call. (<a href="https://redirect.github.com/JelteF/derive_more/pull/322">#322</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/JelteF/derive_more/blob/master/CHANGELOG.md">derive_more's changelog</a>.</em></p> <blockquote> <h2>1.0.0 - 2024-08-07</h2> <p>More than 8 years after the first commit and almost 5 years after the 0.99.0 release, <code>derive_more</code> has finally reached its 1.0.0 release. This release contains a lot of changes (including some breaking ones) to make it easier to use the derives and make it possible to extend them without having to break backwards compatibility again. There are five major changes that I would like to call out, but there are many more changes that are documented below:</p> <ol> <li>There is a new <code>Debug</code> derive that can be used to easily customize <code>Debug</code> formatting.</li> <li>A greatly improved <code>Display</code> derive, which allows you to do anything that <a href="https://github.com/dtolnay/thiserror"><code>thiserror</code></a> provides, but it works for any type not just errors. And by combining the <code>Display</code> derive with the <code>Error</code> and <code>From</code> derives, there shouldn't really be any need to use <code>thiserror</code> anymore (if you are missing a feature/behaviour from <code>thiserror</code> please report an issue).</li> <li>Traits that can return errors now return a type that implements <code>Error</code> when an error occurs instead of a <code>&'static str</code>.</li> <li>When using <code>use derive_more::SomeTrait</code> the actual trait is also imported not just the derive macro. This is especially useful for <code>Error</code> and <code>Display</code></li> <li>The docs are now rendered on docs.rs and are much better overall.</li> </ol> <h3>Breaking changes</h3> <ul> <li>The minimum supported Rust version (MSRV) is now Rust 1.75.</li> <li>Add the <code>std</code> feature which should be disabled in <code>no_std</code> environments.</li> <li>All Cargo features, except <code>std</code>, are now disabled by default. The <code>full</code> feature can be used to get the old behavior of supporting all possible derives.</li> <li>The <code>TryFrom</code>, <code>Add</code>, <code>Sub</code>, <code>BitAnd</code>, <code>BitOr</code>, <code>BitXor</code>, <code>Not</code> and <code>Neg</code> derives now return a dedicated error type instead of a <code>&'static str</code> on error.</li> <li>The <code>FromStr</code> derive now uses a dedicated <code>FromStrError</code> error type instead of generating unique one each time.</li> <li>The <code>Display</code> derive (and other <code>fmt</code>-like ones) now uses <code>#[display("...", (<expr>),*)]</code> syntax instead of <code>#[display(fmt = "...", ("<expr>"),*)]</code>, and <code>#[display(bound(<bound>))]</code> instead of <code>#[display(bound = "<bound>")]</code>. So without the double quotes around the expressions and bounds.</li> <li>The <code>Debug</code> and <code>Display</code> derives (and other <code>fmt</code>-like ones) now transparently delegate to the inner type when <code>#[display("...", (<expr>),*)]</code> attribute is trivially substitutable with a transparent call. (<a href="https://redirect.github.com/JelteF/derive_more/pull/322">#322</a>)</li> <li>The <code>DebugCustom</code> derive is renamed to just <code>Debug</code> (gated now under a separate <code>debug</code> feature), and its semantics were changed to be a superset of <code>std</code> variant of <code>Debug</code>.</li> <li>The <code>From</code> derive doesn't derive <code>From<()></code> for enum variants without any fields anymore. This feature was removed because it was considered useless in</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
fb5fd77b04 |
Bump anyhow from 1.0.91 to 1.0.92 (#1311)
Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.91 to 1.0.92. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/anyhow/releases">anyhow's releases</a>.</em></p> <blockquote> <h2>1.0.92</h2> <ul> <li>Support Rust 1.82's <code>&raw const</code> and <code>&raw mut</code> syntax inside <code>ensure!</code> (<a href="https://redirect.github.com/dtolnay/anyhow/issues/390">#390</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
f83c63c8e8 |
Bump serde_json from 1.0.128 to 1.0.132 (#1309)
Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.128 to 1.0.132. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>1.0.132</h2> <ul> <li>Improve binary size and compile time for JSON array and JSON object deserialization by about 50% (<a href="https://redirect.github.com/serde-rs/json/issues/1205">#1205</a>)</li> <li>Improve performance of JSON array and JSON object deserialization by about 8% (<a href="https://redirect.github.com/serde-rs/json/issues/1206">#1206</a>)</li> </ul> <h2>1.0.131</h2> <ul> <li>Implement Deserializer and IntoDeserializer for <code>Map<String, Value></code> and <code>&Map<String, Value></code> (<a href="https://redirect.github.com/serde-rs/json/issues/1135">#1135</a>, thanks <a href="https://github.com/swlynch99"><code>@swlynch99</code></a>)</li> </ul> <h2>1.0.130</h2> <ul> <li>Support converting and deserializing <code>Number</code> from i128 and u128 (<a href="https://redirect.github.com/serde-rs/json/issues/1141">#1141</a>, thanks <a href="https://github.com/druide"><code>@druide</code></a>)</li> </ul> <h2>1.0.129</h2> <ul> <li>Add <a href="https://docs.rs/serde_json/1/serde_json/struct.Map.html#method.sort_keys"><code>serde_json::Map::sort_keys</code></a> and <a href="https://docs.rs/serde_json/1/serde_json/enum.Value.html#method.sort_all_objects"><code>serde_json::Value::sort_all_objects</code></a> (<a href="https://redirect.github.com/serde-rs/json/issues/1199">#1199</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
6ec7a2fff0 |
Bump insta from 1.40.0 to 1.41.1 (#1307)
Bumps [insta](https://github.com/mitsuhiko/insta) from 1.40.0 to 1.41.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mitsuhiko/insta/releases">insta's releases</a>.</em></p> <blockquote> <h2>1.41.1</h2> <h2>Release Notes</h2> <ul> <li>Re-release of 1.41.0 to generate release artifacts correctly.</li> </ul> <h2>Install cargo-insta 1.41.1</h2> <h3>Install prebuilt binaries via shell script</h3> <pre lang="sh"><code>curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-installer.sh | sh </code></pre> <h3>Install prebuilt binaries via powershell script</h3> <pre lang="sh"><code>powershell -c "irm https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-installer.ps1 | iex" </code></pre> <h2>Download cargo-insta 1.41.1</h2> <table> <thead> <tr> <th>File</th> <th>Platform</th> <th>Checksum</th> </tr> </thead> <tbody> <tr> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-aarch64-apple-darwin.tar.xz">cargo-insta-aarch64-apple-darwin.tar.xz</a></td> <td>Apple Silicon macOS</td> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-aarch64-apple-darwin.tar.xz.sha256">checksum</a></td> </tr> <tr> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-apple-darwin.tar.xz">cargo-insta-x86_64-apple-darwin.tar.xz</a></td> <td>Intel macOS</td> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-apple-darwin.tar.xz.sha256">checksum</a></td> </tr> <tr> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-pc-windows-msvc.zip">cargo-insta-x86_64-pc-windows-msvc.zip</a></td> <td>x64 Windows</td> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-pc-windows-msvc.zip.sha256">checksum</a></td> </tr> <tr> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-unknown-linux-gnu.tar.xz">cargo-insta-x86_64-unknown-linux-gnu.tar.xz</a></td> <td>x64 Linux</td> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-unknown-linux-gnu.tar.xz.sha256">checksum</a></td> </tr> <tr> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-unknown-linux-musl.tar.xz">cargo-insta-x86_64-unknown-linux-musl.tar.xz</a></td> <td>x64 MUSL Linux</td> <td><a href="https://github.com/mitsuhiko/insta/releases/download/1.41.1/cargo-insta-x86_64-unknown-linux-musl.tar.xz.sha256">checksum</a></td> </tr> </tbody> </table> <h2>1.41.0</h2> <ul> <li> <p>Experimental support for binary snapshots. <a href="https://redirect.github.com/mitsuhiko/insta/issues/610">#610</a> (Florian Plattner)</p> </li> <li> <p><code>--force-update-snapshots</code> now causes <code>cargo-insta</code> to write every snapshot, regardless of whether snapshots fully match, and now implies <code>--accept</code>. This allows for <code>--force-update-snapshots</code> to update inline snapshots' delimiters and indentation.</p> <p>For the previous behavior of <code>--force-update-snapshots</code>, which limited writes to snapshots which didn't fully match, use <code>--require-full-match</code>. The main difference between <code>--require-full-match</code> and the existing behavior of <code>--force-update-snapshots</code> is a non-zero exit code on any snapshots which don't fully match.</p> <p>Like the previous behavior or <code>--force-update-snapshots</code>, <code>--require-full-match</code> doesn't track inline snapshots' delimiters or indentation, so can't update if those don't match. <a href="https://redirect.github.com/mitsuhiko/insta/issues/644">#644</a></p> </li> <li> <p>Inline snapshots only use <code>#</code> characters as delimiters when required. <a href="https://redirect.github.com/mitsuhiko/insta/issues/603">#603</a></p> </li> <li> <p>Warnings for undiscovered snapshots are more robust, and include files with custom snapshot extensions. <a href="https://redirect.github.com/mitsuhiko/insta/issues/637">#637</a></p> </li> <li> <p>Insta runs correctly on packages which reference rust files in a parent path. <a href="https://redirect.github.com/mitsuhiko/insta/issues/626">#626</a></p> </li> <li> <p>Warnings are printed when any snapshot uses a legacy format. <a href="https://redirect.github.com/mitsuhiko/insta/issues/599">#599</a></p> </li> <li> <p><code>cargo insta --version</code> now prints a version. <a href="https://redirect.github.com/mitsuhiko/insta/issues/665">#665</a></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mitsuhiko/insta/blob/master/CHANGELOG.md">insta's changelog</a>.</em></p> <blockquote> <h2>1.41.1</h2> <ul> <li>Re-release of 1.41.1 to generate release artifacts correctly.</li> </ul> <h2>1.41.0</h2> <ul> <li> <p>Experimental support for binary snapshots. <a href="https://redirect.github.com/mitsuhiko/insta/issues/610">#610</a> (Florian Plattner)</p> </li> <li> <p><code>--force-update-snapshots</code> now causes <code>cargo-insta</code> to write every snapshot, regardless of whether snapshots fully match, and now implies <code>--accept</code>. This allows for <code>--force-update-snapshots</code> to update inline snapshots' delimiters and indentation.</p> <p>For the previous behavior of <code>--force-update-snapshots</code>, which limited writes to snapshots which didn't fully match, use <code>--require-full-match</code>. The main difference between <code>--require-full-match</code> and the existing behavior of <code>--force-update-snapshots</code> is a non-zero exit code on any snapshots which don't fully match.</p> <p>Like the previous behavior of <code>--force-update-snapshots</code>, <code>--require-full-match</code> doesn't track inline snapshots' delimiters or indentation, so can't update if those don't match. <a href="https://redirect.github.com/mitsuhiko/insta/issues/644">#644</a></p> </li> <li> <p>Inline snapshots only use <code>#</code> characters as delimiters when required. <a href="https://redirect.github.com/mitsuhiko/insta/issues/603">#603</a></p> </li> <li> <p>Warnings for undiscovered snapshots are more robust, and include files with custom snapshot extensions. <a href="https://redirect.github.com/mitsuhiko/insta/issues/637">#637</a></p> </li> <li> <p>Insta runs correctly on packages which reference rust files in a parent path. <a href="https://redirect.github.com/mitsuhiko/insta/issues/626">#626</a></p> </li> <li> <p>Warnings are printed when any snapshot uses a legacy format. <a href="https://redirect.github.com/mitsuhiko/insta/issues/599">#599</a></p> </li> <li> <p><code>cargo insta --version</code> now prints a version. <a href="https://redirect.github.com/mitsuhiko/insta/issues/665">#665</a></p> </li> <li> <p><code>insta</code> now internally uses <code>INSTA_UPDATE=force</code> rather than <code>INSTA_FORCE_UPDATE=1</code>. (This doesn't affect users of <code>cargo-insta</code>, which handles this internally.) <a href="https://redirect.github.com/mitsuhiko/insta/issues/482">#482</a></p> </li> <li> <p><code>cargo-insta</code>'s integration tests continue to grow over the past couple of versions, and now offer coverage of most of <code>cargo-insta</code>'s interface.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
e151f2ab6e |
Bump tokio from 1.40.0 to 1.41.0 (#1308)
Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.40.0 to 1.41.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tokio/releases">tokio's releases</a>.</em></p> <blockquote> <h2>Tokio v1.41.0</h2> <h1>1.41.0 (Oct 22th, 2024)</h1> <h3>Added</h3> <ul> <li>metrics: stabilize <code>global_queue_depth</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6854">#6854</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6918">#6918</a>)</li> <li>net: add conversions for unix <code>SocketAddr</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6868">#6868</a>)</li> <li>sync: add <code>watch::Sender::sender_count</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6836">#6836</a>)</li> <li>sync: add <code>mpsc::Receiver::blocking_recv_many</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6867">#6867</a>)</li> <li>task: stabilize <code>Id</code> apis (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6793">#6793</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6891">#6891</a>)</li> </ul> <h3>Added (unstable)</h3> <ul> <li>metrics: add H2 Histogram option to improve histogram granularity (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6897">#6897</a>)</li> <li>metrics: rename some histogram apis (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6924">#6924</a>)</li> <li>runtime: add <code>LocalRuntime</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6808">#6808</a>)</li> </ul> <h3>Changed</h3> <ul> <li>runtime: box futures larger than 16k on release mode (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6826">#6826</a>)</li> <li>sync: add <code>#[must_use]</code> to <code>Notified</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6828">#6828</a>)</li> <li>sync: make <code>watch</code> cooperative (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6846">#6846</a>)</li> <li>sync: make <code>broadcast::Receiver</code> cooperative (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6870">#6870</a>)</li> <li>task: add task size to tracing instrumentation (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6881">#6881</a>)</li> <li>wasm: enable <code>cfg_fs</code> for <code>wasi</code> target (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6822">#6822</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>net: fix regression of abstract socket path in unix socket (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6838">#6838</a>)</li> </ul> <h3>Documented</h3> <ul> <li>io: recommend <code>OwnedFd</code> with <code>AsyncFd</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6821">#6821</a>)</li> <li>io: document cancel safety of <code>AsyncFd</code> methods (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6890">#6890</a>)</li> <li>macros: render more comprehensible documentation for <code>join</code> and <code>try_join</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6814">#6814</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6841">#6841</a>)</li> <li>net: fix swapped examples for <code>TcpSocket::set_nodelay</code> and <code>TcpSocket::nodelay</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6840">#6840</a>)</li> <li>sync: document runtime compatibility (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6833">#6833</a>)</li> </ul> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6793">#6793</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6793">tokio-rs/tokio#6793</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6808">#6808</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6808">tokio-rs/tokio#6808</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6810">#6810</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6810">tokio-rs/tokio#6810</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6814">#6814</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6814">tokio-rs/tokio#6814</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6821">#6821</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6821">tokio-rs/tokio#6821</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6822">#6822</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6822">tokio-rs/tokio#6822</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6826">#6826</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6826">tokio-rs/tokio#6826</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6828">#6828</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6828">tokio-rs/tokio#6828</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6833">#6833</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6833">tokio-rs/tokio#6833</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6836">#6836</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6836">tokio-rs/tokio#6836</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6838">#6838</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6838">tokio-rs/tokio#6838</a> <a href="https://redirect.github.com/tokio-rs/tokio/issues/6840">#6840</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6840">tokio-rs/tokio#6840</a></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
Daniel Harvey
|
a9f6610691 |
Split resolved metadata from SQL catalog (#1304)
V3_GIT_ORIGIN_REV_ID: 8e64fd6200e207336d18ed6b7c61559fe4b1470d |
||
Vamshi Surabhi
|
6c7ffc270c |
sql introspection: unsupported metadata objects (#1301)
<!-- The PR description should answer 2 important questions: -->
### What
This allows for querying the metadata objects that couldn't be exposed
to the sql layer: such as models, commands, object types, fields of
object types and scalar types. This will help users in debugging their
graph.
### How
Instead of ignoring unsupported metadata objects, we propagate them
through call stacks as required and capture them as part of
introspection tables. Eg. on the duckduckemail API:
```bash
❯ echo 'select * from hasura.unsupported_commands;' | jq --null-input --rawfile sql /dev/stdin '{"sql": $sql}' | curl --silent -XPOST -H 'Content-Type: application/json' -d @- 'http://localhost:3000/v1/sql' | jq
[
{
"subgraph": "app",
"name": "Bye",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "DdaCalendarLoaderInit",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "DdaCalendarLoaderStatus",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "DdaGmailLoaderInit",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "DdaGmailLoaderStatus",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "DdaMyLoaderInit",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "DdaMyLoaderStatus",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "Hello",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "SendEmail",
"reason": "Return type not supported: String! (reason: scalar return types are not supported)"
},
{
"subgraph": "app",
"name": "TestCalendar",
"reason": "Return type not supported: Json! (in subgraph app) (reason: scalar return types are not supported)"
}
]
❯ echo 'select * from hasura.unsupported_scalars;' | jq --null-input --rawfile sql /dev/stdin '{"sql": $sql}' | curl --silent -XPOST -H 'Content-Type: application/json' -d @- 'http://localhost:3000/v1/sql' | jq
[
{
"subgraph": "app",
"name": "Json",
"reason": "No NDC representation found for scalar type 'Json'"
}
]
❯ echo 'select * from hasura.unsupported_object_type_fields;' | jq --null-input --rawfile sql /dev/stdin '{"sql": $sql}' | curl --silent -XPOST -H 'Content-Type: application/json' -d @- 'http://localhost:3000/v1/sql' | jq
[
{
"subgraph": "app",
"object": "CalendarEvents",
"field_name": "attachments",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "CalendarEvents",
"field_name": "conferenceData",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "CalendarEvents",
"field_name": "extendedProperties",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "CalendarEvents",
"field_name": "recurrence",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "CalendarEvents",
"field_name": "reminders",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "GmailMessages",
"field_name": "attachments",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "GmailMessages",
"field_name": "bccAddresses",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "GmailMessages",
"field_name": "ccAddresses",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "GmailMessages",
"field_name": "headers",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "GmailMessages",
"field_name": "labelIds",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
},
{
"subgraph": "app",
"object": "GmailMessages",
"field_name": "toAddresses",
"reason": "Unsupported scalar type: No NDC representation found for scalar type 'Json'"
}
]
❯ echo 'select * from hasura.unsupported_models;' | jq --null-input --rawfile sql /dev/stdin '{"sql": $sql}' | curl --silent -XPOST -H 'Content-Type: application/json' -d @- 'http://localhost:3000/v1/sql' | jq
[]
❯ echo 'select * from hasura.unsupported_object_types;' | jq --null-input --rawfile sql /dev/stdin '{"sql": $sql}' | curl --silent -XPOST -H 'Content-Type: application/json' -d @- 'http://localhost:3000/v1/sql' | jq
[]
```
V3_GIT_ORIGIN_REV_ID: 01aae03d80b0cd15773812fa05a2fd9a57223250
|
||
|
Daniel Harvey
|
ae25f249a2 |
Add more JSONAPI spans (#1297)
<!-- The PR description should answer 2 important questions: --> ### What Lets be a bit more granular about our spans for JSONAPI endpoint. <img width="1508" alt="Screenshot 2024-10-29 at 16 46 32" src="https://github.com/user-attachments/assets/97f67ae3-ac27-4dcd-84a4-083dc6ef5e67"> V3_GIT_ORIGIN_REV_ID: d5c0342c0c9dae2f50e78c7f529a54eeedb541a9 |
||
|
Rakesh Emmadi
|
e15574de67 |
Release v2024.10.30 (#1299)
Update changelog for release v2024.10.30 V3_GIT_ORIGIN_REV_ID: 2bece667c6dedcd596f1ca684d09d42ecf38c1b2 |
||
|
Daniel Harvey
|
5790c088b1 |
Tidy up engine crate (#1296)
<!-- The PR description should answer 2 important questions: --> ### What Needed to reuse some stuff when putting JSONAPI into multitenant, and everything is a big tangled mess, so thought it was finally time to clean up shop. Moves a bunch of stuff from `/bin` into the library in `src` and splits it into files. Functional no-op. V3_GIT_ORIGIN_REV_ID: 87406e3fb63a1f90347782abeda3d4db14386270 |
||
|
Daniel Harvey
|
d5f70fd56a |
More JSONAPI schema tweaks (#1293)
<!-- The PR description should answer 2 important questions: --> ### What A few tweaks to make OpenAPI validators happy. V3_GIT_ORIGIN_REV_ID: a1ff6c7180f1ee02d0e6f53c83aeeceea964e5d8 |
||
|
Rakesh Emmadi
|
a759db7d5a |
graphql-ws: consider comma separated values for protocol header (#1295)
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Consider the possibility of multiple and comma separated header values when validating the protocol name. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 4431eda71e6dcbdbcc2df4520af1ed9cbfe8950d |
||
|
Daniel Harvey
|
1b31f73d26 |
Combine graphql crates together (#1290)
<!-- The PR description should answer 2 important questions: --> ### What Move `lang-graphql`, `graphql-ws` and `frontends/graphql` into the `graphql` folder. Functional no-op. V3_GIT_ORIGIN_REV_ID: c9d6c5db6693dbe9213569443a102a3b3b2e39f6 |
||
|
Rakesh Emmadi
|
1fce83f445 |
graphql-ws: Add Metrics (#1278)
<!-- The PR description should answer 2 important questions: --> ### What Add the following metrics for GraphQL websockets: - active connections - active pollers - total connections <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> ### How This is a bit involved that I initially thought. In normal HTTP requests, metrics are recorded in middleware. In websockets, metrics have to be recorded in deeper layers of code. So made the websocket metrics a part of the `Context` as it is available for each connection. Defined a trait that impls a few methods to record metrics on connection & poller managements, and use them in relevant code paths. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: bbaf63fd7ef3274bf5fe72bb86aa8e07a28f6fe2 |