-
Notifications
You must be signed in to change notification settings - Fork 2.4k
shell: fix sometimes-uninitialized error #16761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for the speedy fix 🚀 |
It's the default on MacOS - which we don't run as part of the PR CI (but only as part of the extended nightly CI). |
Thanks! |
This indeed turned out as error in the nightly CI runs:
great it's already fixed! |
Nice, and I added |
Issue duckdb/duckdb#16250: Window Range Performance (duckdb/duckdb#16765) shell: fix sometimes-uninitialized error (duckdb/duckdb#16761) [Python Dev] Fix the versioning of the nightly python builds (duckdb/duckdb#16739)
Issue duckdb/duckdb#16250: Window Range Performance (duckdb/duckdb#16765) shell: fix sometimes-uninitialized error (duckdb/duckdb#16761) [Python Dev] Fix the versioning of the nightly python builds (duckdb/duckdb#16739)
Issue duckdb/duckdb#16250: Window Range Performance (duckdb/duckdb#16765) shell: fix sometimes-uninitialized error (duckdb/duckdb#16761) [Python Dev] Fix the versioning of the nightly python builds (duckdb/duckdb#16739)
Issue duckdb/duckdb#16250: Window Range Performance (duckdb/duckdb#16765) shell: fix sometimes-uninitialized error (duckdb/duckdb#16761) [Python Dev] Fix the versioning of the nightly python builds (duckdb/duckdb#16739)
Issue duckdb/duckdb#16250: Window Range Performance (duckdb/duckdb#16765) shell: fix sometimes-uninitialized error (duckdb/duckdb#16761) [Python Dev] Fix the versioning of the nightly python builds (duckdb/duckdb#16739)
This is a follow-up to #16594, which introduced the problem.
Thanks to @Tishj for bringing it up here.
(I only encountered the error with
make CXXFLAGS=-Wall
, which makes me wonder a) why that's not the default and b) why CI didn't catch this bug?)