Open kleinschmidt opened 11 months ago
I am not quite sure the bug being reported here. The remotecall_fetch
code extends the serialization code to support moving global variables between compute nodes. That is not part of the standard serialization definition.
The remotecall_fetch code extends the serialization code to support moving global variables between compute nodes. That is not part of the standard serialization definition
Yeah, once I dug more into the ClusterSerializer
I saw that pretty quickly. At this point I think this is more of a documentation issue than anything else.
here's my MWE (tested on 1.9.2):
I understand why the first invocation of my manually-deserialized function doesn't work:
y
is non-const in global scope and is not captured byf
; it works as I'd hoped if I dowhat's troubling me is that somehow when you
remotecall
f
itself,y
gets defined as a global on the worker, so that the second time I deserialize and invokef
on teh remote worker, it succeeds.