Skip to content

fix(dashboard): pin numpy<2 to stop Streamlit Cloud startup segfault - #6

Merged
jackptoke merged 1 commit into
mainfrom
showcase-improvements
Jul 13, 2026
Merged

jackptoke merged 1 commit into
mainfrom
showcase-improvements

Conversation

@jackptoke

Copy link
Copy Markdown
Owner

The dashboard requirements left numpy unpinned, so Streamlit Cloud's resolver installed numpy 2.5.1 on top of the pinned duckdb 1.3.1. Its ABI is incompatible with the older duckdb/pandas/pyarrow wheels loaded at import streamlit, so the app segfaulted on startup — the Cloud log showed "Segmentation fault" and the UI showed only "Error running app".

Pin numpy==1.26.4 (last 1.x, compatible with duckdb 1.3.1 / pandas 2.2.3 / pyarrow 25 / streamlit 1.41.1; resolves cleanly under uv on linux/amd64).

The dashboard requirements left numpy unpinned, so Streamlit Cloud's resolver
installed numpy 2.5.1 on top of the pinned duckdb 1.3.1. Its ABI is incompatible
with the older duckdb/pandas/pyarrow wheels loaded at `import streamlit`, so the
app segfaulted on startup — the Cloud log showed "Segmentation fault" and the UI
showed only "Error running app".

Pin numpy==1.26.4 (last 1.x, compatible with duckdb 1.3.1 / pandas 2.2.3 /
pyarrow 25 / streamlit 1.41.1; resolves cleanly under uv on linux/amd64).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jackptoke
jackptoke merged commit 81770e6 into main Jul 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants