hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 17:31:56 +03:00
Code Issues Projects Releases Wiki Activity
d58ce08c19
graphql-engine/v3/Cargo.toml

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

150 lines
3.7 KiB
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
[workspace]
resolver = "2"
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
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
package.version = "3.0.0"
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
package.edition = "2021"
package.license = "Apache-2.0"
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
members = [
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/auth/*",
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
"crates/compatibility",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/custom-connector",
"crates/engine",
Split out `execute` crate (#588) <!-- Thank you for submitting this PR! :) --> ## Description Following `metadata-resolve` and `schema` crates, this splits out `execute`, the largest folder in `engine`. Undoubtedly this could be split further. Functional no-op. V3_GIT_ORIGIN_REV_ID: c272908153f78212d1f5dd58819707ac3cbcd439
2024-05-17 17:41:32 +03:00
"crates/execute",
`frontends/graphql` crate (#1049) <!-- The PR description should answer 2 important questions: --> ### What This extracts a GraphQL frontend crate from the `execute` crate. This contains all the top level functions, as opposed to what remains in `execute`, which concerns itself with the creation and execution of plans. This only moves code around and organises it a little more neatly, and so makes no functional changes. The follow up will be to create and expose a neater API. Next steps: - Arguably what is left in `execute` is now better named `plan`, but this PR was already big enough. - Once we have more than one `frontend`, the functions in `steps.rs` in this crate should probably be shared somewhere. ### How Moving files around. V3_GIT_ORIGIN_REV_ID: 0e54310a27d06905ed1967395e97ab47751b65dc
2024-09-10 18:09:22 +03:00
"crates/frontends/*",
Rename ir crate to graphql-ir crate (#1116) <!-- The PR description should answer 2 important questions: --> ### What Make what is and is not graphql-centric a little clearer by renaming this crate and moving it into a `crates/graphql` folder. ### How No functional changes V3_GIT_ORIGIN_REV_ID: 3644ce32059e16db9b467b010430ba23fc436ed9
2024-09-17 16:34:04 +03:00
"crates/graphql/*",
Introduce graphql-ws crate that implements GraphQL over websockets (#1134) <!-- 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? --> - Introduce a brand new `graphql-ws` crate that implements - WebSocket request handling by `WebSocketServer` struct - [graphql-ws](https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md) protocol and handles subscriptions in async tokio tasks. - OSS engine now handles GraphQL websockets through `GET /graphql` handshakes. ### How Refer to added [architecture.md](https://github.com/hasura/v3-engine/blob/rakeshkky/graphql-ws-crate/crates/graphql-ws/architecture.md) file. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 3032cbe50267d3f0102c450be2749c09fb3992bf
2024-09-25 16:47:46 +03:00
"crates/graphql-ws",
Empty `jsonapi` crate (#1088) <!-- The PR description should answer 2 important questions: --> ### What Somewhere to put the `jsonapi` proof of concept. ### How Empty crate V3_GIT_ORIGIN_REV_ID: 5675b6fff57e54faa00f05630ae69f8d3471eb7f
2024-09-10 13:25:01 +03:00
"crates/jsonapi",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/lang-graphql",
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
"crates/metadata-resolve",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/metadata-schema-generator",
"crates/open-dds",
Create `plan` crate (#1149) <!-- The PR description should answer 2 important questions: --> ### What We are creating a new build pipeline. This makes a new crate for it called `plan` and puts the existing work from JSONAPI into it. JSONAPI uses the new plan so we have a quick way of testing it works. ### How Mostly moving code around. All behind feature flags, so functional no-op. V3_GIT_ORIGIN_REV_ID: af4901c93415c7ced2b0f537e600512d28fc5766
2024-09-24 17:16:24 +03:00
"crates/plan",
pre-execution plugin middleware (#771) The RFC: https://docs.google.com/document/d/1NB9fA6J8_dKtWknJkfTiqN5qWhPVDfYVOKFK25gYE7Y/edit The JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-234 <!-- The PR description should answer 2 (maybe 3) 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? --> This PR adds a new middleware to the `/graphql` endpoint handler. This new middleware will be used to handle the pre-execution plugins. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> We are doing something similar to https://github.com/tokio-rs/axum/blob/axum-v0.6.20/examples/consume-body-in-extractor-or-middleware/src/main.rs V3_GIT_ORIGIN_REV_ID: a7e0a7a252efd1f266b3e90df23a8307a9b35fc7
2024-07-03 15:57:38 +03:00
"crates/plugins/*",
data shape for query usage analytics (#606) ## Description The expectation is, that engine should emit usages of OpenDD objects (i.e. models, commands, relationships, permissions, fields of types etc.) from a GraphQL query. This PR adds the types required to gather query usage analytics, under a new crate `query-usage-analytics`. V3_GIT_ORIGIN_REV_ID: 49778c25a9019e0c8c9a2d13eaa8ba28638b8b55
2024-05-28 12:50:21 +03:00
"crates/query-usage-analytics",
Experimental SQL interface (#742) Adds a very experimental SQL interface to v3-engine for GenAI use cases. --------- Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> Co-authored-by: Gil Mizrahi <gil@gilmi.net> Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 077779ec4e7843abdffdac1ed6aa655210649b93
2024-06-25 21:45:49 +03:00
"crates/sql",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/utils/*",
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
]
Reduce codegen units to 1 (#964) <!-- The PR description should answer 2 important questions: --> ### What By default, `rustc` splits crates up and builds in parallel. This is faster but misses some optimisations between these sections. Let's reduce it to increase runtime performance. ### How Add settings to `release` profile in `Cargo.toml`. <img width="776" alt="Screenshot 2024-08-13 at 12 59 46" src="https://github.com/user-attachments/assets/a03389dc-80ba-4723-8ca3-36af50846324"> V3_GIT_ORIGIN_REV_ID: 44fa511024140b680b30c9abfaa48034bf0845a9
2024-08-13 16:42:38 +03:00
# generally following guidance from https://nnethercote.github.io/perf-book/build-configuration.html
[profile.release]
codegen-units = 1 # reduce parallelisation to increase optimisations
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
[workspace.lints.clippy]
all = { level = "warn", priority = -1 }
pedantic = { level = "warn", priority = -1 }
Ban `println!` in code with clippy (#711) <!-- Thank you for submitting this PR! :) --> ## Description A few debug lines slipped in recently, let's make `clippy` `warn` on those, so they are kicked out by CI. Functional no-op. V3_GIT_ORIGIN_REV_ID: 290f6de35f9315b68811eb5f15969fb0333e9d06
2024-06-24 14:46:07 +03:00
# ban printing to stdout and stderr
print_stdout = "warn"
print_stderr = "warn"
Remove redundant clones. (#752) I noticed a few extra calls to `.clone()` while working on an unrelated refactor. I want to remove them for brevity and simplicity; I don't expect a performance improvement. This turns on the Clippy warning `redundant_clone`, which detects unnecessary calls to `.clone()` (and `.to_string()`). It is an unstable warning and so might reports some false positives. If we find any, we can suppress the warning there. V3_GIT_ORIGIN_REV_ID: a713f29cf862d6f4cb40300105c6b9f96df00676
2024-06-24 17:08:11 +03:00
# unstable warnings; we might need to suppress them
redundant_clone = "warn"
Use Rust 1.79.0 (#751) <!-- Thank you for submitting this PR! :) --> ## Description Upgrade Rust, as a treat. Functional no-op. --------- Co-authored-by: Samir Talwar <samir@functional.computer> V3_GIT_ORIGIN_REV_ID: 1e0014049e89b8658326c8d8f652df800c415526
2024-06-28 01:21:04 +03:00
# disable this warning until
# https://github.com/rust-lang/rust-clippy/issues/12643 is fixed
manual_unwrap_or_default = "allow"
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
# disable certain pedantic warnings
doc_markdown = "allow"
Semicolons, everywhere! (#700) If a function doesn't return a value, terminate with a semicolon. I also moved `implicit_hasher` and `return_self_not_must_use` to the "definitely keep disabling this" list, and installed [Bacon](https://dystroy.org/bacon/) in the Nix shell to make it easier to run Clippy. V3_GIT_ORIGIN_REV_ID: ffb17b42d982518aec433a1676dba0a0dd0ad95d
2024-06-11 18:32:43 +03:00
implicit_hasher = "allow"
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
missing_errors_doc = "allow"
missing_panics_doc = "allow"
module_name_repetitions = "allow"
must_use_candidate = "allow"
Semicolons, everywhere! (#700) If a function doesn't return a value, terminate with a semicolon. I also moved `implicit_hasher` and `return_self_not_must_use` to the "definitely keep disabling this" list, and installed [Bacon](https://dystroy.org/bacon/) in the Nix shell to make it easier to run Clippy. V3_GIT_ORIGIN_REV_ID: ffb17b42d982518aec433a1676dba0a0dd0ad95d
2024-06-11 18:32:43 +03:00
return_self_not_must_use = "allow"
Apply a few lints to make it struct construction clearer. (#661) 1. Always name the struct when calling `default()`. 2. Sort construction according to the definitions. 3. Approve allowing `struct_field_names` because it doesn't seem to be helpful. 4. Enable `manual_string_new`; nothing seems to be triggering it now. V3_GIT_ORIGIN_REV_ID: 868742114b0bf27bc3ea03cdf1e63a0f710ebe33
2024-06-04 11:42:01 +03:00
struct_field_names = "allow"
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
wildcard_imports = "allow"
Pass `Configuration` by reference, for clearer intent (#1010) ### What Passing `Configuration` by reference signals intent (there is only ever one configuration that is given at the toplevel which is never altered) better than owning and copying values. While in its current state it requires slightly more memory to pass a reference to a `Configuration` rather than a value, this does not seem like the thing to optimize for when it inhibits readability. V3_GIT_ORIGIN_REV_ID: e5e05ad2e7ee41dfb49173ec9575de17552c63ae
2024-08-23 17:00:43 +03:00
trivially_copy_pass_by_ref = "allow"
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
# disable these for now, but we should probably fix them
result_large_err = "allow"
similar_names = "allow"
too_many_arguments = "allow"
too_many_lines = "allow"
unreadable_literal = "allow"
used_underscore_binding = "allow"
fix cargo doc warnings (#585) ## Description As advertised. Now you can run the following to browse our internal code ``` cargo doc --no-deps --document-private-items --open ``` V3_GIT_ORIGIN_REV_ID: 5b7091a00ed6148b8a91168807b07aa6a925cac9
2024-05-16 12:04:07 +03:00
[workspace.lints.rustdoc]
private_intra_doc_links = "allow"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
[workspace.dependencies]
Add Exists in Nested Collection to `Expression` type (#1027) <!-- The PR description should answer 2 important questions: --> ### What Add exists in nested collection to our internal `Expression` type so we can use it in NDC requests. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: b8c2454e35667074a8814844d80430fc765ccdab
2024-08-28 18:48:02 +03:00
ndc-models = { git = "https://github.com/hasura/ndc-spec.git", rev = "54baf298b5d6a69f12a701e9f0e3ce8f188a194d" } # When you update this tag, also update the schema references in crates/open-dds/src/data_connector.rs
Use ndc-models 0.1.6 (#1013) <!-- The PR description should answer 2 important questions: --> ### What Update `v3-engine` to use `ndc-models` 0.1.6. ### How Update in Cargo.toml, check everything builds. V3_GIT_ORIGIN_REV_ID: 64d8b5b8126f593c10ffa89ba21791f326aefedd
2024-08-26 16:46:12 +03:00
ndc-models-v01 = { package = "ndc-models", git = "https://github.com/hasura/ndc-spec.git", tag = "v0.1.6" }
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
anyhow = "1"
apollo-parser = "0.7"
async-graphql-parser = "7"
async-recursion = "1"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
async-trait = "0.1"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
axum = "0.6"
base64 = "0.22"
bincode = "1"
Introduce graphql-ws crate that implements GraphQL over websockets (#1134) <!-- 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? --> - Introduce a brand new `graphql-ws` crate that implements - WebSocket request handling by `WebSocketServer` struct - [graphql-ws](https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md) protocol and handles subscriptions in async tokio tasks. - OSS engine now handles GraphQL websockets through `GET /graphql` handshakes. ### How Refer to added [architecture.md](https://github.com/hasura/v3-engine/blob/rakeshkky/graphql-ws-crate/crates/graphql-ws/architecture.md) file. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 3032cbe50267d3f0102c450be2749c09fb3992bf
2024-09-25 16:47:46 +03:00
blake2 = "0.10.6"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
bson = "2"
build-data = "0.2"
bytes = "1"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
chrono = "0.4"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
clap = "4"
convert_case = "0.6"
cookie = "0.18"
criterion = "0.5"
darling = "0.20"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
datafusion = "41"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
derive_more = "0.99"
diffy = "0.4"
env_logger = "0.11"
expect-test = "1"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
futures = "0.3"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
futures-util = "0.3"
goldenfile = "1"
graphql-parser = "0.4"
http = "0.2"
human_bytes = "0.4"
indexmap = "2"
insta = "1"
json_value_merge = "2"
JSONAPI build plan (#1114) <!-- The PR description should answer 2 important questions: --> ### What Let's get to a very basic end-to-end pipeline. This introduces (extremely-happy-path) planning, execution and response processing so that we have a rough end to end API. V3_GIT_ORIGIN_REV_ID: 57ce28eb5ad20f061e0ede37b0bf43fbaddaaf2a
2024-09-17 18:44:12 +03:00
jsonapi_library = { package = "jsonapi", git = "https://github.com/hasura/jsonapi-rust.git", rev = "b908b340ddfc620d33b71f279b88a0233bd5ff5c" }
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
jsonptr = "0.4"
jsonwebkey = "0.3"
jsonwebtoken = "8"
Introduce graphql-ws crate that implements GraphQL over websockets (#1134) <!-- 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? --> - Introduce a brand new `graphql-ws` crate that implements - WebSocket request handling by `WebSocketServer` struct - [graphql-ws](https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md) protocol and handles subscriptions in async tokio tasks. - OSS engine now handles GraphQL websockets through `GET /graphql` handshakes. ### How Refer to added [architecture.md](https://github.com/hasura/v3-engine/blob/rakeshkky/graphql-ws-crate/crates/graphql-ws/architecture.md) file. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 3032cbe50267d3f0102c450be2749c09fb3992bf
2024-09-25 16:47:46 +03:00
lazy_static = "1.5.0"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
lexical-core = "0.8"
Use mimalloc (#961) <!-- The PR description should answer 2 important questions: --> ### What We started using `mimalloc` allocator in MBS a while ago with good results, let's use it here too. Once `v3-engine-multitenant` is merged we should use it there too. ### How Import crate, switch it on in engine binary and in benchmarks. <img width="845" alt="Screenshot 2024-08-13 at 10 10 49" src="https://github.com/user-attachments/assets/dc872668-1633-468a-86d3-51fca5be68bf"> V3_GIT_ORIGIN_REV_ID: ebad91bb57964477d0f227e341c7bd12d54f0f68
2024-08-13 12:54:08 +03:00
mimalloc = "0.1"
CI: Fix the Rust cache. (#942) ### What Try not to pollute the CI cache with the wrong thing. ### How 1. Remove the package selector as we don't care about production builds here any more. 2. Tell the test build to not save the cache so there is no write contention. 3. Downgrade `mockito` to v1.4 reduce the size of the cache, because `v1.5` depends on `http` v1. V3_GIT_ORIGIN_REV_ID: 2109c8c7db5d80e3b2c29d2949423e8faebd10b2
2024-08-07 18:02:33 +03:00
mockito = { version = "~1.4", default-features = false } # v1.5+ depends on http v1
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
nonempty = "0.10"
openssl = "0.10"
Bump opentelemetry to 0.23 (#1160) And bump other opentelemetry-* deps to compatible with 0.23 <!-- 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? --> Need [add_link](https://docs.rs/opentelemetry/0.23.0/opentelemetry/trace/trait.Span.html#tymethod.add_link) API on Spans for tracing `graphql-ws` websockets code. It is available opentelementry version `0.23` and above. This also bumps all the dependents of the opentelemetry crate (`opentelemetry-*`) ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> By updating root `Cargo.toml`. V3_GIT_ORIGIN_REV_ID: 87c1bedde35f5e8e91366aceb1379ab5d43b5b99
2024-09-26 17:44:02 +03:00
opentelemetry = "0.23"
opentelemetry-contrib = "0.15"
opentelemetry-http = "0.12"
opentelemetry-otlp = "0.16"
opentelemetry-semantic-conventions = "0.15"
opentelemetry-stdout = { version = "0.4", default-features = false }
opentelemetry-zipkin = "0.21"
opentelemetry_sdk = "0.23"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
postcard = "1"
pretty_assertions = "1"
proc-macro2 = "1"
quote = "1"
rand = "0.8"
ref-cast = "1"
regex = "1"
reqwest = "0.11"
rmp-serde = "1"
Validate that the capabilities version matches the DataConnectorLink schema version (#880) This PR adds validation code to `metadata_resolve` that prevents someone from putting a schema/capabilities from the wrong NDC version into the DataConnectorLink while specifying a different schema version in the DataConnectorLink. For example: ``` kind: DataConnectorLink version: v1 definition: name: data_connector schema: version: v0.2 schema: {} capabilities: version: 0.1.5 # Not allowed for version v0.2! capabilities: {} ``` This PR has two commits. One is a refactor where we rearrange the DataConnectorError types so that the name of the data connector is captured centrally in `NamedDataConnectorError`, so that it doesn't have to be passed around and included in every error manually. The other is the validation changes to `metadata_resolve`. Completes APIPG-705 V3_GIT_ORIGIN_REV_ID: baed571f36f4cbed824ca546128f5df360d5b298
2024-07-25 17:30:31 +03:00
semver = "1.0"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
schemars = "0.8"
serde = "1"
serde_json = "1"
serde_path_to_error = "0.1"
serde_with = "3"
sha2 = "0.10"
smol_str = "0.1"
strum = "0.26"
strum_macros = "0.26"
syn = "2"
thiserror = "1"
tokio = "1"
tokio-test = "0.4"
tower = "0.4"
tower-http = "0.4"
tracing = "0.1"
tracing-subscriber = "0.3"
transitive = "0.5"
url = "2"
Introduce graphql-ws crate that implements GraphQL over websockets (#1134) <!-- 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? --> - Introduce a brand new `graphql-ws` crate that implements - WebSocket request handling by `WebSocketServer` struct - [graphql-ws](https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md) protocol and handles subscriptions in async tokio tasks. - OSS engine now handles GraphQL websockets through `GET /graphql` handshakes. ### How Refer to added [architecture.md](https://github.com/hasura/v3-engine/blob/rakeshkky/graphql-ws-crate/crates/graphql-ws/architecture.md) file. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 3032cbe50267d3f0102c450be2749c09fb3992bf
2024-09-25 16:47:46 +03:00
uuid = "1"
Reference in New Issue Copy Permalink