Closing a connection fails
- Dominant language
- C++
- Stars
- 91
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Hi all,
This is an issue following this DuckDB [discussion](https://github.com/duckdb/duckdb/discussions/10397#discussioncomment-8393044), and it might also be related to Issue: https://github.com/duckdb/duckdb-node/issues/39
What happens is, after successfully closing a connection the first time, any subsequent connection cannot be closed anymore.
To reproduce, please clone this [quick repo](https://github.com/dusadrian/ducktest).
After the usual `npm install` to get all necessary node packages, use `npm start` to start the application and push the button.
After no longer than 30 seconds, the database lock is released and I can connect using either CLI from the Terminal, or from another API such as the `duckdb` package in R.
However, *after* the first lock being released, for any subsequent button push (therefore any subsequent database connection), the lock is not released anymore no matter how much time one waits.
This was tested on MacOS on both Intel and ARM computers, using Sonoma.
The DuckDB version is the latest, 0.10.0 (as per the `package.json` file in the above repo.
In hoping this can be reproduced,
Adrian
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.