vivian-rook commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-223495
This error still appears in an upgrade from superset 3.1.1 (helm chart
0.12.7) to 4.0.1 (helm chart 0.12.11)
--
This is an automated message from the Apache Git Service.
To
toniphan21 commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2096473674
I think [this PR](https://github.com/apache/superset/pull/28357) will also
fix this problem.
--
This is an automated message from the Apache Git Service.
To respond to the
ichux commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2089937122
> I patched the file with this attached patch and I was able to get it
working. I think this is a hack, but it's got me past the problem.
>
> filename: sql_parse.patch
>
gthomas-strike commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2088938047
We are encountering the same issue with a deployment using the latest
`0.12.9` helm chart version
--
This is an automated message from the Apache Git Service.
To respond
rusackas commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2075062237
Pinging @michael-s-molina @dpgaspar in case they see a better way to provide
a generalized fix/migration for others getting stuck. Otherwise, I hope the
change above resolves
Umkqq commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2074948455
> I patched the file with this attached patch and I was able to get it
working. I think this is a hack, but it's got me past the problem.
>
> filename: sql_parse.patch
>
dagostinelli commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2074894134
I patched the file with this attached patch and I was able to get it
working. I think this is a hack, but it's got me past the problem.
filename: sql_parse.patch
Umkqq commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2074872710
I am experiencing the same issue. Using PostgreSQL version 12.18 and docker
deployment based on latest superset image. Deployed from scratch and using
empty database.
Issue is
dagostinelli commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2073807516
Here's a screenshot:
--
This is an automated message from the
dagostinelli commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2073806789
I have this same problem. I experienced it during an upgrade. Old superset
was based on an older Github commit. New superset is based on whatever is
currently in
AutumnSun1996 commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2068498360
and there is no use or modify with jinja, just some simple queries.
BTW, I'm now using force cast 'self.sql' to str inside the
'ParsedQuery.stripped' method as a
AutumnSun1996 commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2068488275
The problem first appears with our test env, which use mysql:8.
But I can reproduce it using sqlite, with reproduce steps above, so I think
it's related to superset
rusackas commented on issue #28145:
URL: https://github.com/apache/superset/issues/28145#issuecomment-2067286158
Hmmm... can't reproduce this one so far. Are you using any particular DB, or
doing anything fancy with jinja?
--
This is an automated message from the Apache Git Service.
To
AutumnSun1996 opened a new issue, #28145:
URL: https://github.com/apache/superset/issues/28145
### Bug description
Cannot accesse 'Query history' page, and get empty list with this error:
14 matches
Mail list logo
