nigzak
nigzak
UDPATE: +++ IGNORE THIS COMMENT +++ Found an issue in the deployment configuration - the feature flag was configrued TWICE, one time with the flag, one time without it ......
could be a duplicate ticket to https://github.com/apache/superset/issues/18634 (happens also on V1.5.x)
could be a duplicate ticket to https://github.com/apache/superset/issues/19988 (happens also on V2.0.0)
Hi @rusackas I have added both driver in my container (still like this :)) and I am using currently CHROME variant. I have shortly checked the official documentation again on...
FYI: if the change is made it should be updated to 4.14.x (or newer) to fix a CVE finding (refer linked https://github.com/apache/superset/issues/26992)
Hi @rusackas the pull request here seems to update it to V4.10.x - only have in mind it should be updated to >= V4.14.x (newer as it is in this...
Hi @rusackas can you let me know how to do this? Make a "copy" of it in discussion thread? I sadly did not find a button to move it to...
I am not sure, if it is inside why is docker scout showing that it is problematic? Pulled today via "docker pull apache/superset:3.1.0" and open in scout still shows 9.5.0...
superset 3.1.1 seems NOT to be affected 
close as it seems it is not wanted to highlight well known bugs/cve's in images which are shown in public repos/docker scout FYI @michael-s-molina this is the same behaviour as...