-
Notifications
You must be signed in to change notification settings - Fork 86
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
CLEANUP: Deprecation of multiprocess (since Oct 2020) #546
Comments
The next step in deprecating 'multiprocess' could be to make it become the same as 'sequential' regardless of argument |
You can remove AlpsNMR from this list, since I backported the deprecation fix to the release branch (and it's released already) |
Starting with next release of future (>= 1.28.0-9001), there will be one deprecation warning produced per 'multiprocess' future created. This may be very noisy, but that's on purpose. For example, > library(future)
> plan(multiprocess)
Warning message:
Strategy 'multiprocess' is deprecated in future (>= 1.20.0) [2020-10-30]. Instead, explicitly specify either 'multisession' (recommended) or 'multicore'. In the current R session, 'multiprocess' equals 'multicore'.
> y <- future.apply::future_lapply(1:3, FUN = sqrt)
Warning messages:
1: Detected creation of a 'multiprocess' future. Strategy 'multiprocess' is deprecated in future (>= 1.20.0) [2020-10-30]. Instead, explicitly specify either 'multisession' (recommended) or 'multicore'. In the current R session, 'multiprocess' equals 'multicore'.
2: Detected creation of a 'multiprocess' future. Strategy 'multiprocess' is deprecated in future (>= 1.20.0) [2020-10-30]. Instead, explicitly specify either 'multisession' (recommended) or 'multicore'. In the current R session, 'multiprocess' equals 'multicore'.
3: Detected creation of a 'multiprocess' future. Strategy 'multiprocess' is deprecated in future (>= 1.20.0) [2020-10-30]. Instead, explicitly specify either 'multisession' (recommended) or 'multicore'. In the current R session, 'multiprocess' equals 'multicore'.
> |
UPDATE 2023-01-17: Next step is to turn 'multiprocess' into 'sequential' processing; still with those warnings |
…ntial); same for multiprocess() -> sequential() [#546]
I've made 'multiprocess' defunct when running interactive mode, while keeping it deprecated in batch mode (e.g.
|
I've decided to make |
…are four packages failing as expected [ci skip] [#546]
future 1.32.0 is on CRAN, where 'multiprocess' is now defunct. The next step will be to remove
I'm gonna close this issue and deal with the above at a later time. |
Packages on CRAN and Bioconductor that use 'multiprocess'
Last updated: 2023-03-21
Currently,
multiprocess
is defunct, but still exists. Whenmultiprocess
is removed in a later version, it will break 3 CRAN packages (and zero Bioconductor packages):PeakSegDisk
if(interactive() && requireNamespace("future"))future::plan("multiprocess")
."multiprocess"
, it will not break when themultiprocess
function is removed.tcplfit2
tcplfit2::hitcont()
is called withmc.cores > 1
. Usesplan(multiprocess, workers = mc.cores)
.import(future)
, so whenmultiprocess
is removed from future, this package will still load, butR CMD check
will produce a NOTE (or a WARNING?).TSstudio
Blocker: maintainer cannot update due to contract with their employer (2022-04-12)
ts_grid()
usesfuture::plan(future::multiprocess, workers = n.cores)
which is called whenparallel = TRUE
, which is the default.If you see this and are a maintainer of one of the above packages, please replace
multiprocess
withmultisession
. Themultiprocess
backend is defunct as of future 1.32.0 (2023-03-07), i.e. give an error if used.Additional non-CRAN, non-Bioconductor packages
Completed
Last updated 2023-03-21.
Packages that fail checks because 'multiprocess' is now defunct
future 1.32.0 is on CRAN as of 2023-03-07. This broke 3 CRAN packages and 1 Bioconductor package.
dhReg
fiery
prewas
MineICA
Resolved
AlpsNMR
alookr
blockCV
flowGraph
geocmeans
greta
ipc
kernelboot
protti
rBiasCorrection
RTransferEntropy
seer
SpaDES.core
tsfeatures
Moot, because removed from CRAN or Bioconductor (last updated 2022-06-02)
biotmle
EpiNow2
fipe
The text was updated successfully, but these errors were encountered: