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
Although batchExport() successfully exports variables starting with periods, they are not loaded in the job sessions. This is in turn because loadExports() does not load those variables.
If fixed, the list.files() call of fail:::Ls() needs all.files=TRUE in order to pick up variables starting with a period. Simple tests, indicates that this is enough, that is, with .c in keys, then f$assign(keys, envir = .GlobalEnv) does indeed load and assign .c to the global environment.
The text was updated successfully, but these errors were encountered:
Although
batchExport()
successfully exports variables starting with periods, they are not loaded in the job sessions. This is in turn becauseloadExports()
does not load those variables.Example
Troubleshooting
All four variables are indeed exported:
But the
ls()
method for fail objects inloadExports()
uses the defaultall.files=FALSE
;Suggestions
batchExport()
should give an error, or at least a warning, if variable names starting with a period are specified, cf. Issue batchExport() and objects with non-standard names #93.list.files()
call offail:::Ls()
needsall.files=TRUE
in order to pick up variables starting with a period. Simple tests, indicates that this is enough, that is, with.c
inkeys
, thenf$assign(keys, envir = .GlobalEnv)
does indeed load and assign.c
to the global environment.The text was updated successfully, but these errors were encountered: