Win10, long-lived processes - "system error 232, The pipe is being closed" about processx HOT 5 OPEN

You can try to write the output into a file, then no pipe is needed, and this error should go away, or at least manifest in a different way.

from processx.

Can you please show a reproducible example?

from processx.

I will try; I'm struggling to reproduce it reliably myself, because of the dependence on waiting days or weeks to provoke it.

from processx.

Thanks, I'll try that as well when I manage to setup a proper testbed.

(I'm really sorry for the lack of reprex since I've posted this - I'm not ignoring that, I just have not had the chance to set things up!)

from processx.

No worries at all, no rush at my end. It could also help if you could show some (possibly simplified) version of your code, even if it does not reproduce the problem for a long time.

I did some searching, and there is a very small chance that it is this:
https://stackoverflow.com/a/43070326/604364
I say very small, because I am pretty sure that processx handles reading no data from the pipe properly.

If I had to guess I would say that it is probably a race condition in processx, but some code could help me make a better guess.

from processx.