Hasura local console error "parsing RQLMetadata failed, expected Object, but encountered Array"

[nicaura]

Version Information

Server Version: v2.16.0 CLI Version (for CLI related issue): v2.16.0

Environment

Local docker image hasura/graphql-engine:v2.16.0

What is the current behaviour?

Everytime we tried to update metadata through the console launched through hasura console we get the following error :

{ "code": "parse-failed", "error": "parsing RQLMetadata failed, expected Object, but encountered Array", "path": "$" }

What is the expected behaviour?

Metadata yaml files to be updated locally.

How to reproduce the issue?

1. hasura console
2. Update any metadata

Please provide any traces or logs that could help here.

From the Chrome console :

Any possible solutions/workarounds you're aware of?

Update metadata manually.

[sounden]

Hi!

I had the exact same issue and it drove me mad, it seem like if you turn off migrations from the console this happens.

So make sure to have it on, at least it worked for me.

Have a nice day!

[harishnair96]

Providing simple repro steps for the engineering team -

1. Create an untracked table -

   CREATE TABLE table1(id SERIAL PRIMARY KEY, field TEXT);
   

2. Make sure migrations are disabled -
3. Try to track the table -

Issue exists even in v2.19.0-beta.1.

[phamquyhai]

It has not been fixed yet

[mrpotato3]

+1

[initplatform]

Wasted a cool 3 hours on that one until I found this issue :/

running v2.47.0

How about just a heads up to turn on migrations instead of this error that leads to nowhere