-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GH-38382: [R] Explicitly clean up arrow_duck_connection()
on exit
#38495
Conversation
|
@amoeba Can you give this a quick review? All the R CI jobs are currently failing due to a dbplyr update and this PR contains a fix! |
Hey @paleolimbot, this looks good to me. Thanks for taking care if both things. |
@github-actions crossbow submit -g r |
Revision: 9b9186a Submitted crossbow builds: ursacomputing/crossbow @ actions-0487ce50cd |
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 57c028f. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 7 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…exit (apache#38495) ### Rationale for this change We get lots of warning messages about unclosed connections when running tests + users get them on exit when they weren't expecting them. ### What changes are included in this PR? A finalizer was added on exit to close the global arrow_duck_con that we cache in the global options. ### Are these changes tested? Yes, the finalizer will run in every test that runs `to_duckb()` with the default connection. ### Are there any user-facing changes? No. * Closes: apache#38382 Authored-by: Dewey Dunnington <dewey@fishandwhistle.net> Signed-off-by: Nic Crane <thisisnic@gmail.com>
…38495) ### Rationale for this change We get lots of warning messages about unclosed connections when running tests + users get them on exit when they weren't expecting them. ### What changes are included in this PR? A finalizer was added on exit to close the global arrow_duck_con that we cache in the global options. ### Are these changes tested? Yes, the finalizer will run in every test that runs `to_duckb()` with the default connection. ### Are there any user-facing changes? No. * Closes: #38382 Authored-by: Dewey Dunnington <dewey@fishandwhistle.net> Signed-off-by: Nic Crane <thisisnic@gmail.com>
…exit (apache#38495) ### Rationale for this change We get lots of warning messages about unclosed connections when running tests + users get them on exit when they weren't expecting them. ### What changes are included in this PR? A finalizer was added on exit to close the global arrow_duck_con that we cache in the global options. ### Are these changes tested? Yes, the finalizer will run in every test that runs `to_duckb()` with the default connection. ### Are there any user-facing changes? No. * Closes: apache#38382 Authored-by: Dewey Dunnington <dewey@fishandwhistle.net> Signed-off-by: Nic Crane <thisisnic@gmail.com>
Rationale for this change
We get lots of warning messages about unclosed connections when running tests + users get them on exit when they weren't expecting them.
What changes are included in this PR?
A finalizer was added on exit to close the global arrow_duck_con that we cache in the global options.
Are these changes tested?
Yes, the finalizer will run in every test that runs
to_duckb()
with the default connection.Are there any user-facing changes?
No.