Closed johndharrison closed 7 years ago
Yes, AFAIR you're right. I've been working on an alternative read code where one can wait on both output streams, it's in a separate branch now (wait-for-both-streams
). I think I did fix a timeout issue there. I'll merge it soon.
Hi @johndharrison, could you please see if the issue has been fixed for you? It seems to be fixed in my environment.
Hi @lbartnik
that has fixed the issue I was having. The return from process_read where pipe != "both" is inconsistent across platforms however. Mac/osx are returning a list (for example list(stdout = "ddfsdg")) linux is returning just the character vector.
I prefer a list to be returned for all pipe settings (so that res[["stderr"]] will just return NULL if the pipe = "stdout") but either way is fine.
Hi @johndharrison, it's strange what you write about Mac because all platforms pass the same set of tests. I'll keep the output as it is for now but maybe you're right.
Hi @lbartnik yes I must not have been running the most recent branch as process_read is working as expected cross-platform now. Thanks
Running the above i get:
I had expected subprocess to check for output to stderr for 1 second if none found return character(0).