Closed irinakhismatullina closed 5 years ago
On it.
@irinakhismatullina What are the local versions of
I cannot reproduce it.
modelforge==0.9.3
asdf==2.3.1
So @irinakhismatullina I cannot reproduce it in Travis, too: https://travis-ci.org/src-d/modelforge/builds/490553316
Looks like you have to debug this yourself. Reproduce a working environment (in docker) and then compare the two behaviors.
@irinakhismatullina Ping
I haven't looked into it since then, in my model I used workaround described above. Seeing that you couldn't reproduce the bug, probably the issue may be closed.
OK, py 3.5 support is dropped anyway.
Faced problems with multiprocessing inside loaded modelforge model. Happens both in lazy and not lazy load modes.
Here is the code sample, reproducing error:
Test non-lazy mode:
Here is the output:
Same with multithreading:
Gets:
Same happens in lazy mode. Calling this functions in original class instance works fine.
This fixes the problem locally (can be done inside _load_tree()):
It passes, but looks like numpy arrays non-lazy loading is meant to work right out-of-the-box.