-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Fix update extensions #17527
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
Fix update extensions #17527
Conversation
|
Testing I think should happen via https://github.com/carlopi/duckdb/actions/runs/15093857243 / extension update workflow (that is currently failing). I will review that once that's in. |
|
Failure looks to me to be not-connected, but would be handy to restart to double check since both are in the area of networking. To me Python one looks to be random network failure, and |
|
https://github.com/duckdb/duckdb/actions/runs/15093832916/job/42426425248?pr=17527 looks to be a missing ORDER BY in that test. |
I think it's the macro that should probably perform the ORDER BY, or at least I would assume logs to be ordered. |
|
Thanks! |
Absorb patch from duckdb/duckdb#17527
This includes both removing patch from duckdb#17527 and fix from duckdb/duckdb-httpfs#57
This includes both removing patch from #17527 and fix from duckdb/duckdb-httpfs#57
Fix update extensions (duckdb/duckdb#17527) [Python Dev] Using `reinterpret_steal` breaks the refcount of the passed-in object (duckdb/duckdb#17525)
Fix update extensions (duckdb/duckdb#17527) [Python Dev] Using `reinterpret_steal` breaks the refcount of the passed-in object (duckdb/duckdb#17525)
Fix update extensions (duckdb/duckdb#17527) [Python Dev] Using `reinterpret_steal` breaks the refcount of the passed-in object (duckdb/duckdb#17525)
Fix update extensions (duckdb/duckdb#17527) [Python Dev] Using `reinterpret_steal` breaks the refcount of the passed-in object (duckdb/duckdb#17525)
This restore the following workflows to work as intended:
and the same with
httpfsloaded:Note that this is relevant only for UPDATE EXTENSIONS or for the INSTALL codepath for an already installed extension.
Also, without this PR the behaviour would be long waits on
UPDATE EXTENSIONS, that would eventually timeout and resume normal execution.It's not completely clear to me why both
follow_locationandkeep_aliveneeds to be set to false, whether this has something to do with our current setup to serve extensions or else, but this restore to the defaults in place before the HTTPUtil rework.