FileHandles aren't closed outside of C++ destructors - leading to unhandled I/O exceptions. about duckdb HOT 4 CLOSED

Super cool extension!

I don't think there is any real way to do this at the moment, but for logging the error to some structure your extension owns, and then say rethrow at a later point that you control.

from duckdb.

Thank you @carlopi, it feels really good that you liked the extension. I appreciate your compliment! DuckDB is awesome.

The problem is that the popen()'ed process's error should be associated with the executing query. So deferring notification to the user is kind of hard to do, but I'm going to think about your suggestion.

from duckdb.

I don't see exactly either, it can be possibly hacked on, say by rewriting the query to be the regular query + a shellfs callback/cleanup, or something equivalent, but query execution is NOT my area, someone more at ease will pass with some feedback.

from duckdb.

If the pclose() is called when the read() returns zero, any error reported are properly raised in the context of query execution.

from duckdb.