Skip to content
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

Please do not change future options #1

Closed
HenrikBengtsson opened this issue Feb 29, 2024 · 8 comments
Closed

Please do not change future options #1

HenrikBengtsson opened this issue Feb 29, 2024 · 8 comments

Comments

@HenrikBengtsson
Copy link

HenrikBengtsson commented Feb 29, 2024

Hello. Please do not set future options from within your package, as in:

parseRPDR/R/ZZZ.R

Lines 1 to 4 in aec45d7

.onAttach <- function(libname, pkgname) {
options(future.globals = TRUE)
options(future.globals.maxSize = +Inf)
options(future.chunk.size = 1.0)

R options are meant for end-users, not developers. If you need to tweak the settings, please do so temporarily, as explained in https://future.futureverse.org/articles/future-7-for-package-developers.html#avoid-changing-the-future-options.

@CAndrewBasham
Copy link

CAndrewBasham commented Mar 1, 2024 via email

@HenrikBengtsson
Copy link
Author

Just checking back in on this one. I see you submitted on parseRPDR 1.1.1 on 2024-04-03 to CRAN, after I filed this issue.

@martonkolossvary
Copy link
Owner

martonkolossvary commented Dec 15, 2024 via email

@HenrikBengtsson
Copy link
Author

HenrikBengtsson commented Dec 15, 2024

Hi.

Please see what I wrote and the link I refer to in my top comment. I'm asking you to not set this when the package is attached. You can still set it temporarily inside the functions where you need it. https://future.futureverse.org/articles/future-7-for-package-developers.html#avoid-changing-the-future-options has almost cut'n'pastable instructions for how to do this.

Also, there are no future R options future.globals and future.chunk.size, so those you can drop.

@HenrikBengtsson
Copy link
Author

I and lots of people using futureverse would appreciate it if you fixed this. As I said, the fix is possible.

@martonkolossvary
Copy link
Owner

martonkolossvary commented Jan 25, 2025 via email

@HenrikBengtsson
Copy link
Author

HenrikBengtsson commented Jan 25, 2025

Oh, I see. Great. Thanks. I didn't see any commits or updates here in this repository, which still has the old code - I guess they still need to be pushed here.

@martonkolossvary
Copy link
Owner

martonkolossvary commented Jan 25, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants