Containers crash with module 'sqlglot.expressions' has no attribute 'YearOfWeek'

[mueller-ma]

Bug description

1. Update from 6.0.0 to 6.1.0 using docker compose

Screenshots/recordings

No response

Superset version

6.1.0

Python version

Not applicable

Node version

Not applicable

Browser

Not applicable

Additional context

docker compose up -d

Docker logs from superset-worker-beat-1:

Installing superset-core in editable mode
Resolved 1 package in 1ms
   Building apache-superset-core @ file:///app/superset-core
      Built apache-superset-core @ file:///app/superset-core
Prepared 1 package in 484ms
Uninstalled 1 package in 0.53ms
warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
         If the cache and target directories are on different filesystems, hardlinking may not be supported.
         If this is intentional, set `export UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.
Installed 1 package in 1ms
 ~ apache-superset-core==0.1.0rc3 (from file:///app/superset-core)
Skipping local overrides
Starting Celery beat...
Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help.

Error:
Unable to load celery application.
Module 'sqlglot.expressions' has no attribute 'yearofweek'

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[rusackas]

@dosu any ideas on this one?

[dosubot]

Hey @rusackas — this looks like a sqlglot version mismatch.

The YearOfWeek expression class was introduced in sqlglot v28 [1], but the current Superset codebase pins sqlglot to >=26.1.3, <27 [2], resolving to sqlglot==26.28.1 [3]. So official Superset shouldn't reference YearOfWeek at all with its pinned dependency.

A couple of things stand out:

1. There is no official Superset 6.1.0 release — the latest tag is 5.0.0. So @mueller-ma may be using an unofficial Docker image or third-party packaging that bundles a mismatched sqlglot version.

2. The likely scenario: the environment has Superset code that was built against sqlglot v28+ (which has exp.YearOfWeek), but the installed sqlglot is actually v26 which lacks it — or vice versa: sqlglot v28+ is installed but old Superset code tries to import something that doesn't exist yet. Either way, the dependency versions are out of sync.

Workaround for the reporter: exec into the container and run pip show sqlglot to check the version. If it's v28+, downgrading to match the constraint (pip install "sqlglot>=26.1.3,<27") should resolve it. But the real fix is using an official Superset Docker image at a valid release tag (e.g., apache/superset:4.1.1 or apache/superset:5.0.0).

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[mueller-ma]

There is no official Superset 6.1.0 release — the latest tag is 5.0.0.

There is: https://github.com/apache/superset/releases/tag/6.1.0

[fowlerp397-tech]

Thanks for the correction. The assumption about 6.1.0 not being an official release is outdated. Given that this is occurring on an official 6.1.0 upgrade, the more interesting question is why the environment ends up with a "sqlglot" version that doesn't provide "sqlglot.expressions.yearofweek" while the Superset code expects it. Could you share: - The exact image tag you're upgrading from and to - Whether you're using the official "docker-compose-image-tag.yml" setup or a customized image - The output of "pip show sqlglot" (or "uv pip show sqlglot") inside the failing container That should help determine whether this is a dependency resolution issue during the upgrade or a packaging problem in the 6.1.0 images.

…

On Tue, Jun 23, 2026, 3:47 AM mueller-ma ***@***.***> wrote: *mueller-ma* left a comment (apache/superset#41280) <#41280 (comment)> There is no official Superset 6.1.0 release — the latest tag is 5.0.0. There is: https://github.com/apache/superset/releases/tag/6.1.0 — Reply to this email directly, view it on GitHub <#41280?email_source=notifications&email_token=B72HASOCPBQ53UM6EBLIUN35BI73ZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZXG4ZTSNZVGU2KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4777397554>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B72HASP7OL6OIRBGESKSD3T5BI73ZAVCNFSNUABEKJSXA33TNF2G64TZHMZTSNBWGQYDCOB3JFZXG5LFHM2DOMJUGU3TANBQG6QXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B72HASPKVWGZHZN4ZQN3T7L5BI73ZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZXG4ZTSNZVGU2KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B72HASIJJQQJOXOFFQRMHND5BI73ZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZXG4ZTSNZVGU2KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mueller-ma]

When I start completely fresh (stop all containers, remove all containers, images and volumes), starting 6.1.0 works using docker compose up and the default configs. When updating from 6.0.0 sqlglot isn't updated:

$ git checkout 6.0.0
$ docker compose up
$ docker exec -it superset_worker_beat bash uv pip show sqlglot
Name: sqlglot
Version: 27.15.2
Location: /app/.venv/lib/python3.11/site-packages
Requires:
Required-by: apache-superset
$ docker compose down
$ git checkout 6.1.0
$ docker compose up
$ docker exec -it superset-superset-worker-beat-1 uv pip show sqlglot
Name: sqlglot
Version: 27.15.2
Location: /app/.venv/lib/python3.11/site-packages
Requires:
Required-by: apache-superset, apache-superset-core

(Output of some commands removed)