NOT FOR MERGING: Isolate hang in Arrow test #86
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR shows a minimal change that leads to
dbSendQuery(arrow = TRUE)
hanging.Test code:
On the main branch of this repo, this code works. On the commit "Harmless parts" from this PR, the code works. On the commit "Remove special case", it does not terminate.
This change is part of duckdb v0.10.0. I'd like to resolve this before proceeding with the CRAN release.
I also tested with
SET threads = 1
, same result.Upstream: duckdb/duckdb#10245 (comment)
The first commit in this PR corresponds to the main branch just before merging duckdb/duckdb#10245. The last two commits are a decomposition of duckdb/duckdb@68c9e1a.
@Tmonster: Can you replicate