(1.3.4-beta.2) action relationship with permissions

Trying out 1.3.4 beta 2 today (from 1.3.3) and I have run into multiple issues. Haven’t had issues upgrading before. PostgreSQL 11.5

1. Hasura wouldn’t start due to hyphens in primary keys. This worked previously. {"type":"startup","timestamp":"2020-12-22T16:14:35.348+0000","level":"error","detail":{"kind":"catalog_migrate","info":{"path":"$","error":"cannot include "article-article_category_pk" in the GraphQL schema because it is not a valid GraphQL identifier",“code”:“validation-failed”}}} .` I refactored those to remove the error.

2. Then, I got an error on a previously working Action query. I’m not using hasura.user anywhere in code. I finally restarted the server and it went away. "error": { "path": "$", "error": "unrecognized configuration parameter \"hasura.user\"", "code": "constraint-error" },

3. Now, I’m getting “invalid input syntax for type json” from the same action. "error": { "path": "$", "error": "invalid input syntax for type json", "code": "data-exception" },

It’s a simple action–not sure where to go from here: type GetHomeContentOutput { postId : Int }

[tirumaraiselvan]

I have been able to reproduce this and forwarded to our engineering team. Thanks for the report!

The issue seems to arise when using a role and action relationships (with permissions on the relationship table). I also recvd the two errors on different runs which is really weird:

"error": { "path": "$", "error": "unrecognized configuration parameter \"hasura.user\"", "code": "constraint-error" },

and

"error": { "path": "$", "error": "invalid input syntax for type json", "code": "data-exception" },

[tirumaraiselvan]

Thanks @jacdx . I was on holidays last few days. I will check your repro today.