Open jstammers opened 1 year ago
@jstammers thanks for reporting. What duckdb version are you using?
I remember in earlier Duckdb versions (<3), I often saw segment fault but in later versions I have never seen this happening.
One problem I saw in unit tests of duckdb is that it can have weird behaviors because the duckdb connection are not properly closed at certain step so the following steps are having issues.
Hi @goodwanghan, thanks for looking into this. I'm currently using 0.7.1
which I believe is the latest version.
It wouldn't surprise me if it's related to trying to a previous duckdb connection not being properly closed, but for now I will stick with the fugue API.
Minimal Code To Reproduce
Describe the bug I have a set of unit tests that check the functionality of code that uses the
fugue_sql
API with a DuckDB backend. When running these tests locally, they all pass without any issue. However, when I run these as part of a Github actions workflow, I frequently encounter a segmentation fault that occurs at the following locationThe function that fails has the following form
And I have multiple unit tests that call this function. It's difficult to fully isolate the problem as I can't fully reproduce it locally.
In this instance, I have been able to refactor my function to use the fugue api, but it would be good to be able to use the fugue_sql API for more complex queries where the SQL syntax is more suitable.
Expected behavior I would expect these unit tests to run successfully.
Environment (please complete the following information):