bump out-of-tree extensions to v1.2.2#16913
bump out-of-tree extensions to v1.2.2#16913Mytherin merged 8 commits intoduckdb:v1.2-histrionicusfrom
Conversation
|
|
|
The Windows error message is also weird, my explanation would be persistent secret being shared across tests (?), and iceberg being auto-loaded first and then autoloading avro on load. Or even if not exactly that, it points to something off. |
|
Actually also the "Checks extension entries" is connected: |
|
@Tmonster: I think almost ready, but for aws failure in Windows CI: windows failure need fixing aws side? this means the secret type needs registering duckdb side? |
|
Relevant failing test for AWS |
carlopi
left a comment
There was a problem hiding this comment.
Looks about right! Thanks
Co-authored-by: Carlo Piovesan <[email protected]>
carlopi
left a comment
There was a problem hiding this comment.
Thanks again.
This should likely be good, and after latest change (that include duckdb/duckdb-aws#74), this should also fix the Windows and Wasm CI issues
|
@Mytherin: this is still expected to fail, since arrow and possibly other extensions have not been adapted yet, BUT given this is now failing later, and this contain still relevant logic to handle |
|
Sure - thanks! |
bump out-of-tree extensions to v1.2.2 (duckdb/duckdb#16913)
bump duckdb-httpfs, and duckdb-aws to latest version of v1.2-histrionicus
Also removing
DONT_LINKfrom avro since duckdb-iceberg tries to automatically load it, and if it is not available duckdb-iceberg will through an error. This means any time iceberg is autoloaded and avro is not available/linked, then statements/tests will fail.EDIT: not bumping iceberg in this PR. Want to try and isolate errors.
EDIT2: Not bumping aws, there seems to be an issue with windows and provider
credential_chain. Want to try and debug it on the windows laptop first