Sebastian Hoffmann

@ejguan If I am not mistaken, this has been fixed by https://github.com/pytorch/pytorch/pull/97287 and can be closed? Correct me if I am wrong. Thanks for the fix

Unfortunately, no. The errors during import in the worker processes are due to my environment being screwed up and import order actually matters in in that regard. I unfortunately currently...

I suppose having a module that checks, during import, whether the current process is a child process and if so throws an error would be sufficient to provoke this.

Sorry for the late reply, I was kind of the busy. I already fixed this; however I ammended the commit and did a force push. Unfortunately travis CI doesn't seem...

Ok, I'll have another look at it today or tommorrow

Indeed, pytorch migrated to C++17 half a year ago: https://github.com/pytorch/pytorch/commit/36ac095ff8918bf7c208029bf6ad28418f1620c1 It thus might and can assume that downstream dependencies require C++17. I'm still not sure whether the flatbuffer library in...

After further investigation I can confirm that a `libabseil` (conda) package is likely included from a newer version of libprotobuf. I'm not where the protobuf dependency stems from exactly though....

I support this endeavor. Instead of completely removing torch as dependency, I would welcome it already, if all parts of trochdata were contained in this package instead of being split...

If I have not lacked any crucial point in the documentation, we have timeouts for opening and closing handshakes aswell as pings. However I talked about timeouts at application level....

As a user, I find the topic very unclear and would hope that were to be a clear and concise way to do this in the future. In essence, I...