Rob Dominguez
Rob Dominguez
This appears to be a bug where the configured prefix is lost from `__typename `when aliasing remote relationship fields. Since the prefix becomes part of the actual type name in...
The spike isn’t directly correlated to the raw size of the YAML files, but to how the engine expands and validates the permissions, allow-lists, and query collections when applying metadata....
Thanks for this, @bbetters — let me check with our SRE and Infra folks who are more familiar with deploying to k8s.
This appears to be AI-generated with a few outdated concepts and issues, @0NIKHIL0. Have you been through this guide yourself?
@dmeth94 — can you please provide some steps to reproduce this error?
@dmeth94 — you can see the domain in the error: ```plaintext https://graphql-engine-cdn.hasura.io ``` Alternatively, if this is the issue, you can load the assets directly using [this environment variable](https://hasura.io/docs/2.0/deployment/graphql-engine-flags/config-examples/#console-assets-on-server): ```...
If no one else on your team is having this issue, I'd recommend allowing `https://graphql-engine-cdn.hasura.io` via your filter. Additionally, if this started 2 days ago, it'd be helpful to think...
I've passed this onto the folks who work on the console; we'll get back to you ASAP.