Thijs
Thijs
Yea there are requirements, the compilation will fail if those are not met, I ran into those when I tried a random `BLOCK_ALLOC_SIZE`, as it needs to be a multiple...
I changed the `test_block_sizes.py` and `test_vector_sizes.py` files, seeing as I have to make another commit anyways to revert the nightly test stuff I'll push it after the relevant test finishes...
@taniabogatsch it didn't complete successfully, but I'm not sure the failures are related to these changes?
Seems to pass the nightly tests:
Also please don't make use of the upstream CI (by clicking Ready to Review) as we are building a release candidate and would like all the runners available for that...
@Tmonster is this a failure on `feature` as well? It feels unrelated to my changes @maiadegraaf actually, might be related to your profiling changes?
https://github.com/duckdb/duckdb/pull/11524
Hey sorry, I wasn't clear The problem is introduced by that PR, I just wanted to point to the relevant context There is no real reason the ALTER you're doing...
> 11 errors Can you provide these?
Can you try this to troubleshoot? You say this crashes: ```py import duckdb duckdb.sql("select 42") ``` Does this also crash? ```py import duckdb duckdb.default_connection.sql("select 42") ``` ```py import duckdb con...