Manas Agarwal

Hi @jgoux, thank you for opening this issue. In general, Hasura is considered healthy even if there are inconsistencies in the schema, because it can continue to serve for the...

Hi @gneeri , thanks for opening this issue. We have been able to identify the root cause of this issue. The server is responding with `ping` for every `pong` from...

This has been addressed in release v2.13. Closing this issue. Please re-open if the issue persists. Thanks.

Hi @fungilation, thank you for opening the issue. We are currently evaluating Graphiql 2 and the efforts involved in the upgradation. We will update once we have more information on...

Hi @sameelTabir, thank you for opening this issue. It's not yet clear to us what the actual error is and where it comes from. Could you please add some more...

Hi @andoks , thank you for bringing this issue to our attention. We are currently investigating this and would update soon with our findings.

Hi @ilovett , thanks for opening this issue. As per this [doc](https://hasura.io/docs/latest/hasura-cli/config-reference/), one can provide a custom `env` file which can act an alternative to a custom config file. e.g....

Hi @sankara-sabapathy, thank you for opening this issue. It's not yet clear to us what the actual error is and where it comes from. Could you please add some more...

This bug is accepted and has been kept in the Platform team backlog.

`--disallow-inconsistent-metadata` flag is now supported since 2.11 now. Can this issue be considered resolved?