You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under the above given setting the following warning message appears when e.g. LDARep is executed: 1: In sprintf(...) : one argument not used by format 'Exporting objects to package env on master for mode: %s'
If you are running LDARep locally, however, the following message should appear: Exporting objects to package env on master for mode: local
This is a warning resulting from parallelMap::parallelExport, explicitly from the line showInfoMessage("Exporting objects to package env on master for mode: %s", mode, collapse(objnames)).
There is only one conversion specification %s, but two arguments, which results in the warning.
This will not be fixed, because the development of parallelMap is retired and this is an unwanted behavior that does not necessarily need to be corrected. Instead, the ldaPrototype package will replace parallelMap with the future package in the long run.
The text was updated successfully, but these errors were encountered:
Under the above given setting the following warning message appears when e.g.
LDARep
is executed:1: In sprintf(...) : one argument not used by format 'Exporting objects to package env on master for mode: %s'
If you are running
LDARep
locally, however, the following message should appear:Exporting objects to package env on master for mode: local
This is a warning resulting from
parallelMap::parallelExport
, explicitly from the lineshowInfoMessage("Exporting objects to package env on master for mode: %s", mode, collapse(objnames))
.There is only one conversion specification
%s
, but two arguments, which results in the warning.This will not be fixed, because the development of
parallelMap
is retired and this is an unwanted behavior that does not necessarily need to be corrected. Instead, theldaPrototype
package will replaceparallelMap
with thefuture
package in the long run.The text was updated successfully, but these errors were encountered: