[
https://issues.apache.org/jira/browse/ARROW-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601357#comment-17601357
]
Dewey Dunnington commented on ARROW-17643:
------------------------------------------
The error is almost certainly a result of `arrow::Status::Invalid(e.what())`
where the exception is a `cpp11::unwind_exception()` (Or some other exception
that doesn't have `what()` overridden:
Probably in parquet/exception.h:
{noformat}
#define END_PARQUET_CATCH_EXCEPTIONS \
} \
catch (const ::parquet::ParquetStatusException& e) { \
return e.status(); \
} \
catch (const ::parquet::ParquetException& e) { \
return ::arrow::Status::IOError(e.what()); \
}
{noformat}
> [R] Latest duckdb release is causing test failure
> -------------------------------------------------
>
> Key: ARROW-17643
> URL: https://issues.apache.org/jira/browse/ARROW-17643
> Project: Apache Arrow
> Issue Type: Bug
> Components: R
> Reporter: Dewey Dunnington
> Priority: Major
>
> The latest duckdb release was just put on CRAN (0.5.0), and when it's
> installed we get a test failure:
> {noformat}
> ── Error (test-duckdb.R:212:3): Joining, auto-cleanup enabled
> ──────────────────
> Error: rapi_execute: Failed to run query
> Error: Invalid Error: std::exception
> Backtrace:
> ▆
> 1. ├─DBI::dbGetQuery(...) at test-duckdb.R:212:2
> 2. └─DBI::dbGetQuery(...)
> 3. └─DBI (local) .local(conn, statement, ...)
> 4. ├─DBI::dbSendQuery(conn, statement, ...)
> 5. └─duckdb::dbSendQuery(conn, statement, ...)
> 6. └─duckdb (local) .local(conn, statement, ...)
> 7. └─duckdb:::duckdb_result(...)
> 8. └─duckdb:::duckdb_execute(res)
> 9. └─duckdb:::rapi_execute(...)
> [ FAIL 1 | WARN 1 | SKIP 28 | PASS 8460 ]
> Error: Test failures
> Execution halted
> Warning messages:
> 1: Connection is garbage-collected, use dbDisconnect() to avoid this.
> 2: Database is garbage-collected, use dbDisconnect(con, shutdown=TRUE) or
> duckdb::duckdb_shutdown(drv) to avoid this.
> 1 error ✖ | 0 warnings ✔ | 2 notes ✖
> {noformat}
> Unfortunately I can't reproduce this on either MacOS nor Ubuntu (20.04).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
