4.1.0rc3

[sadpandajoe]

Hello Superset Community,

This is a call for the vote to release Apache Superset version 4.1.0.

The release candidate:
https://dist.apache.org/repos/dist/dev/superset/4.1.0rc3/

The Git tag for the release:
https://github.com/apache/superset/tree/4.1.0rc3

The CHANGELOG for the release:
https://github.com/apache/superset/blob/4.1.0rc3/CHANGELOG/4.1.0.md

The instructions for updating to the release:
https://github.com/apache/superset/blob/4.1.0rc3/UPDATING.md

Public keys are available at:
https://www.apache.org/dist/superset/KEYS

---

This discussion was created from the release 4.1.0rc3.

[gpchandran]

Hello ,
My smoke testing looks good with 4.1.rc3, when you're planning 4.1.0 release tentatively?

[sadpandajoe]

Following the releasing page:

Once 3+ binding votes (by PMC members) have been cast and at least 72 hours have past

so could be as early as Monday or could be later depending on how things are voted.

[jacob-roldan]

Is there an error to get the PDF or image in the latest version??

#30645

[gpchandran]

Hello ,
getting 404 not found error on below API calls
https:///api/v1/dashboard/46/screenshot/c15f73c3387df8f2583bd50b1f4a0dc4/?download_format=pdf
https:///api/v1/dashboard/46/screenshot/c15f73c3387df8f2583bd50b1f4a0dc4/?download_format=png

is this functionality working for you or other? not sure it's my environment or Superset application issue. I'm sure it's working for me on previous version 4.0.2

[gpchandran]

hi @geido - is this PDF/Image download works for you?

[sadpandajoe]

@gpchandran I believe @geido has a PR out (linked to the issue) that will make download work as it did before by moving the new logic behind a feature flag.

[geido]

@gpchandran you must have cache and Celery configured for this to work. If you have, then you should wait for the task to finish up and the endpoint will return 404 until the image is ready to be pulled from the cache.

[gpchandran]

Thanks a lot @sadpandajoe and @geido - will this PR go in to 4.1.0rc4?
I've both Redis Cache and Celery running on our deployment.
ENABLE_DASHBOARD_DOWNLOAD_WEBDRIVER_SCREENSHOT - is enabling this feature flag mandatory for download PDF/Image feature?

[padbk]

Am trying to test with python 3.11, but found no image on DockerHub #30672

[padbk]

This is merged now. #30733

Will it be possible to get this 🍒 'd so we get 4.1.0 python 3.11 images on Docker Hub please?

[sadpandajoe]

just cherried it, so should be part of rc4

[hscabral]

Is anyone having issues with ModuleNotFoundError: No module named 'psycopg2'? It does not happen in 4.0.2.

[gpchandran]

I faced same issue and added to this lib psycopg2-binary requirements.txt to resolve it

[sfirke]

Yes this is due to a change in how docker images are built.

• Report of this issue on the RC2 thread: 4.1.0rc2 #29999 (comment)
• Resolution: added a note to the 4.1.0 release notes https://github.com/apache/superset/blob/4.1.0rc3/RELEASING/release-notes-4-1/README.md#release-notes-for-superset-410
• I wonder if it should also be added to the UPDATING notes? https://github.com/apache/superset/blob/4.1.0rc3/UPDATING.md

[hscabral]

Building from scratch or running locally is fine. My use case involves downloading the images from Docker Hub to be used in a Kubernetes cluster. In RC3 I was able to make it work downloading the -dev image, but not sure if ideal to what we are doing. The issue seems to be widely reported, so I think I will follow the discussions and progress. In the release note it's fairly outlined too, as I noticed, thanks!

Starting in 4.1.0, the release's docker image does not ship with drivers needed to operate Superset. Users may need to install a driver for their metadata database (MySQL or Postgres) as well as the driver for their data warehouse. This is a result of changes to the lean docker image that official releases come from; see Docker Build Presets for more details.

[sfirke]

@hscabral I think running -dev is an okay approach for now. Ideally there would be a pre-built image available that has some parts of -dev like the headless browser for screenshots and the psycopg2 driver but unlike -dev doesn't run as the root user... if someone wanted to share a Dockerfile for this I could work in December on making that part of the official build process.

[vicky-sai]

Any idea when are we planning for the release ?!
I am wondering the Schema specific access in SQL Lab will work only with this error fix.!

[sadpandajoe]

@vicky-sai did you see if this is resolved in 4.1.0rc3? If not do you have an open issue?

[vicky-sai]

@sadpandajoe
Error: #28596
PR: #29311

This is something which I am awaiting to be fixed..

[sadpandajoe]

@vicky-sai did you see the comment in that PR? Someone mentioned it was fixed with the 4.1.0rc2, have you verified it isn't working? As for the PR you linked, in it's current state it's probably not mergeable as it's failing CI and could break for some databases.

[gpchandran]

Hi, getting this issue in 4.1.0rc3 (this was working fine in 4.0.2), unable to add Custom SQL for tabular chart Column.
Any one facing this issue, is this a bug or new validation added in 4.1? please advise

[gpchandran]

Enabling this ALLOW_ADHOC_SUBQUERY feature flag fixes this issue

[sadpandajoe]

Voting is done and this release did no pass