Data Catalog not populated in v2.4.0

[alex-lucem]

Before Proceeding, please acknowledge:

• I have consulted the Troubleshooting guide.
• I have searched Issues and Discussions in this repo.
• Feature requests should be initiated as Discussions. This is a bug report.

Describe the bug
Updated to the most recent version of Harlequin yesterday, v2.3.0 and then v2.4.0. Even after updating all my drivers, the data catalog no longer displays anything. It will show files but no schema.

All drivers were working previously in v2.1.2

I've tried it with the following drivers:

• postgres (v1.2.2 and v1.3.0)
• bigquery (v1.0.3) (would work for small BQ datasets without the issue mentioned in harlequin-bigquery #13, but now this issue rears its ugly head every time 😢 )
• sqlite

To Reproduce
Steps to reproduce the behavior.

• Start harlequin v2.4.0 with any of the mentioned drivers: bigquery, sqlite, postgres

Expected behavior
I was expecting to see data in the Data Catalog

Actual behavior
The data catalog is completely empty for all drivers mentioned (didn't have DBs to test on others readily available):

(Ignore the dtools thing, that's just a wrapper CLI I make for all my useful commands. This one just spins up a container and runs this exact command: harlequin -a postgres "postgres://postgres:password@localhost:5432/postgres" -f .)

Contributing
Are you interested in contributing a fix?

• Yes
• Maybe
• No

Additional context

• Shell: bash
• Terminal: Wezterm
• OS of the shell: Ubuntu 24.04
• Default locale / language for your OS/Terminal/Shell: en_US/UTF-8

How did you install Harlequin?

• pipx
• conda/mamba
• pip (global install)
• pip + venv/virtualenv or pipenv
• Poetry
• uv/Rye
• other: _____________

[tconbeer]

yeah, I can reproduce with a fresh uv install or pip install from PyPI. It's all adapters. Pythons 3.12-3.14; 3.11 works fine

Can't reproduce when running the project with uv, or when building the project and installing either the whl or sdist with pip.

Same issue in 2.3.0; 2.2.1 is fine.

Seems related to Textualize/textual#6102, which only impacted 3.12+

[alex-lucem]

Fix worked like a charm. Thanks!