Bunny
> @aibunny Thanks for contributing, appreciate it! > > As mentioned in #40, I think it needs to be put under `meta.label`, not just `label` (as this wouldn't show up...
I ran some functional tests because I didn't have any other tests to work with. Basically, I tested different cases: one with a metafield and labels, another with a metafield...
> > I ran some functional tests > > You mean against dbt and Superset? Which versions did you use? Did it work as expected then? yes , I used...
I am also facing this issue though I am using keycloak as my OIDC.
For superset version 3.1.x I didn't experience this issue but for 4.0.x I am experiencing this issue.
This isue happens even on fresh superset installation, even when there are no previously set access permissions or filters applied. I create the dataset/database using the same users I access...
Everything works fine I get a 200 OK statu code on fetch and even when creating I don't encounter any errors the issue is only on fetching. It's weird that...
I don't incluse any query params when fetching, I am using superset 4.0.1. Here are my logs ``` superset_worker_beat | 2024-05-20T09:25:00.049055943Z [2024-05-20 09:25:00,048: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)...
Did you find any error?