[
https://issues.apache.org/jira/browse/ARROW-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601915#comment-17601915
]
Dewey Dunnington commented on ARROW-17643:
------------------------------------------
A few things based on trying a bunch of things yesterday and today:
The error is probably not coming directly from Arrow. There's only one place
where we do {{Status::Invalid(e.what())}} and it's when converting wide strings
to unicode. Also, I added extra error handling stuff such that we never {{throw
cpp11::unwind_exception}} without an explanatory message and that didn't
surface any extra error information. After adding
{{ARROW_EXTRA_ERROR_CONTEXT=ON}} to the docker builds that had been failing, I
wasn't able to replicate the error at all (although this may be because there
was less CI pressure today than yesterday).
I opened an issue on DuckDB to see if they have any ideas:
https://github.com/duckdb/duckdb/issues/4656
> [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
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
