question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possible Bug: Computed Field Permission is not being inferred

See original GitHub issue

Hi there,

I have a computed field, order, for which I believe the inferred permission is incorrect. If my understanding is correct, the permission box is meant to be checked and disabled if the computed field permissions are inferred from the table from which it is derived. However, it is unchecked and not disabled.

image

image

As can be seen below, the permission for the value returned by the sql function is enabled on the table that the computed field is derived from:

image

I am doing metadata programatically so I have to come to the console afterwards and check this box in order for things to work at all!

I have seen this pull request, https://github.com/hasura/graphql-engine/pull/5741, maybe this issue I am having relates to this?

We are using 1.3.2.

Thanks!

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
LydiaFcommented, Jul 1, 2021

Dear Gavin,

Thank you so much for replying so quickly and indeed for helping me fix the issue!!

It was all my fault.

Instead of doing this :

  permission:  {
    computed_fields: [
      'card_order'
    ],
    columns: [...],
    ...
  }
  permission:  {
    columns: ['card_order', ...],
  }

Basically I didn’t know permission.computed_fields was thing. Had a quick check of the docs there and can only see “For scalar computed fields, permissions are managed similar to the columns permissions of the table.” but maybe I’m missing it… I was at the time certainly.

In any case I am glad as now I understand how to find bugs a bit better!

A BIG THANK YOU!

Lydia

1reaction
GavinRay97commented, Jul 2, 2021

That’s awesome to hear! Glad it was something able to be figured out =D

Read more comments on GitHub >

github_iconTop Results From Across the Web

GraphQL : Error while adding computed fields - Stack Overflow
I am able to select the function "fullname" from the dropdown but getting an error on adding computed field. Any guidance is appreciated....
Read more >
Bug descriptions — spotbugs 4.7.3 documentation
This finalizer nulls out fields. This is usually an error, as it does not aid garbage collection, and the object is going to...
Read more >
Method: instances.insert | Compute Engine Documentation
If the source image is deleted later, this field will not be set. Authorization requires the following IAM permission on the specified resource...
Read more >
Troubleshoot connector and format issues in mapping data flows
Learn how to troubleshoot data flow problems related to connector and format in Azure Data Factory.
Read more >
Topics API: developer guide
Not all users are eligible for the Privacy Sandbox Relevance and ... With the Topics API proposal, the browser would infer topics for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found