Closed Someone894 closed 3 years ago
See the 2.0.0 release notes for the motivation (https://www.tidyverse.org/blog/2020/11/magrittr-2-0-is-here/#laziness) and workaround (https://www.tidyverse.org/blog/2020/11/magrittr-2-0-is-here/#sequential-evaluation).
Thank you for your quick reply, I’ve read those blog entries before posting the issue, I just thought they weren’t related to my topic. But it turned out I do have a tricky side effect in my code, I wasn’t aware of.
To speed up the calculation I use a multi-thread approach, where each thread gets a socket to write in a log file and I use 64 threads. As you can see here R only supports 125 sockets (= 128 - 3 (stdin, stdout, stderr)). The lazy evaluation caused the system to open up 64 sockets without performing a calculation and then opening up another 64 sockets, thus exceeding the limit and crashing.
Hello,
I'm using the
%>%
operator quite extensively (sometimes 10 to 20 statements in a row) and I encountered a strange behavior that brakes all my existing code. From Version 1.5 to 2.0.1 the order in which the statements are executed got reversed. Here is a example using Docker:Within the container:
Within R
reload the session to get the new magrittr version going
As you can see the execution order changed from A,B,C to C,B,A. Since my code depends on the order in which the statements come this is important to me. Can you reproduce this behavior and is there a way to obtain the old behavior?