Open DrewScatterday opened 3 days ago
Hi! Thanks for reporting this issue!
My first hunch is that this is related to https://github.com/duckdb/duckdb/issues/13848#issuecomment-2352674000, but the fact that it only crashes when you instantiate the r-tree index is strange... We run the r-tree tests as part of our CI on windows, so maybe it's node related? I'll try to have a look tomorrow.
Thanks @Maxxen !! Let me know what you find out
I can test on a Ubuntu WSL node js env just to help sanity check
Code works with no issues on Ubuntu 22.04.02 and same version of node (20.11.1)
So definitely a windows issue and not a rtree bug hmmm
I tried installing the nightly version of duckdb on winodws with npm install duckdb@next
but the cmd window seems to just hang:
[##################] - reify:duckdb: timing reify:audit Completed in 276ms
edit: uninstalled duckdb and then installed with npm install duckdb@next
and then still got the same issue
The duckdb version that gets installed with npm install duckdb@next
is "duckdb": "^1.0.1-dev27.0"
. Was still getting this issue on that version.
I followed the thread in the issue you linked and did the following:
14.40.33810.0
.duckdb/extensions
npm install duckdb
I then still got same issue
I also tried reinstalling spatial extension with FORCE INSTALL spatial FROM core_nightly;
but I still get that weird error message I got above
Hi! Thanks for your hardwork on DuckDB absolutely loving it in my day to day spatial data work.
I think this may be be related to #391 but not sure. I think I found a bug with r-tree indexing. I'm using example code from this article https://duckdb.org/docs/extensions/spatial/r-tree_indexes#example
I'm using node.js 20.11.1, Windows 10, and duckdb 1.1.0
If I run this code, it dies with no error thrown:
If I remove the r-tree index, it works with no problem:
Output:
I also tried using nightly build:
I get this as the error message:
Any ideas, am I missing something?