Closed mlell closed 1 year ago
This appears to be a duplicate of #285 and should be fixed when updating the ‘globals’ package that ‘future’ depends on.
Ah, yes I can confirm that it works with globals 0.16.2. Should have remembered that my analysis environment is not up to date... thank you for the hint.
Error description
The future package implements promise objects and flexible switching between parallel worker setups independent of analysis code.
It currently is not usable together with imports of the form
box::use(file[...])
because it registers something on the search path thatfuture
cannot read because it expects "normal" packages there.If I write a file
box/test.R
with content:I get an error with this:
I want to file a bug report to "future" but I do not know a constructive suggestion because I am not familiar with the internals of "box".
At the end, future needs to read properties from "box" environments that are sufficient to load those modules on the worker.
I know that I can extract information using
pos.to.env()
andattributes()
:Is it enough to write some function that scrapes the needed information, e.g. from
$spec$prefix
,$spec$name
, and$spec$attach
? Are these informations stable acrossbox
versions?Finally, I need to work around the non-standard evaluation of
box::use
usingcall()
or similar... Is there a way to call a non-NSE version ofuse()
to avoid that?R version
‘box’ version
1.1.0