Graphql-engine: TypeError: Cannot convert undefined or null to object

Created on 6 Nov 2019  路  5Comments  路  Source: hasura/graphql-engine

I am using Hasura v1.0.0-beta 8 on a Docker container with a PostgreSQL v11 database.

I can't modify any of the tables in my database. The interface shows the following error:

TypeError: Cannot convert undefined or null to object at Function.keys (<anonymous>) at n (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/main.js.gz:1:3386804) at Editor.n (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/main.js.gz:1:629171) at Ha (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2639858) at Wa (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2639651) at Ya (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2643090) at fs (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2665500) at ds (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2665890) at Zs (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2673066) at Ys (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2672434)

Any help?

Thanks.

console bug urgent

Most helpful comment

This will be fixed in a few hours.

Meanwhile please refer to https://github.com/hasura/graphql-engine/issues/3314#issuecomment-550540012 for an immediate workaround!

All 5 comments

I have the same error in two instances of Hasura on Heroku,
It's also affecting Hasura v1.0.0-beta 9

TypeError:` Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at n (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/main.js.gz:1:3386804)
    at Editor.n (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/main.js.gz:1:629171)
    at Ha (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2639858)
    at Wa (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2639651)
    at Ya (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2643090)
    at fs (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2665500)
    at ds (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2665890)
    at Zs (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2673066)
    at Ys (https://graphql-engine-cdn.hasura.io/console/assets/channel/beta/v1.0/vendor.js.gz:1:2672434)

There is another user in discord reporting the same problem.
Could you add a label p/urgent k/bug
Thanks

I am using Hasura v1.0.0-beta.9 on a Docker container with a PostgreSQL v10.7 database and also getting same error message when navigate into any table's modify tab.

Using hasura v1.0.0-beta.9 on postgres 11.
Having this issue on every modify tab.

Does anyone have an intermediary rollback solution?

This will be fixed in a few hours.

Meanwhile please refer to https://github.com/hasura/graphql-engine/issues/3314#issuecomment-550540012 for an immediate workaround!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

codepunkt picture codepunkt  路  3Comments

marionschleifer picture marionschleifer  路  3Comments

sachaarbonel picture sachaarbonel  路  3Comments

lishine picture lishine  路  3Comments

stereobooster picture stereobooster  路  3Comments