Re: [PATCH] tee: Add --pipe-check to allow instantly detecting closed outputs

2022-11-27 Thread Arsen Arsenović
Arsen Arsenović writes: > Looking at ``check_output_alive'', this logic should be fairly easy to > reuse. Worst case, I'd need to refactor some of the code to handle the > non-pipe-check case more elegantly so that it doesn't become too > unreadable when also adding the logic to pick between

Re: [PATCH] tee: Add --pipe-check to allow instantly detecting closed outputs

2022-11-27 Thread Pádraig Brady
On 27/11/2022 11:32, Arsen Arsenović wrote: Arsen Arsenović writes: Looking at ``check_output_alive'', this logic should be fairly easy to reuse. Worst case, I'd need to refactor some of the code to handle the non-pipe-check case more elegantly so that it doesn't become too unreadable when

Re: [PATCH] tee: Add --pipe-check to allow instantly detecting closed outputs

2022-11-27 Thread Arsen Arsenović
Hi, Pádraig Brady writes: > I vaguely remember on macos that POLLRDBAND needed to be set on read fds for > select, > though didn't check all combinations since we didn't actually need > the poll() replacement. Also select() (emulation of poll) doesn't work on > Solaris or AIX, so we needed to

bug#59636: prime [ factor ] utility very slow in factoring the square of a prime

2022-11-27 Thread Jason C. Kwan
The test case is        49,456,902,806,087,647,575,555,655,201 a prime that is approx. 95.3-bits in size, plus the direct squaring of it, ascalculated by gnu-bc      (see full text below for host system info,      versioning details, and command line      statements used to perform this test.