Collin Funk

> There is no specified behaviour for non-Unicode encoded byte sequences passed as environment variables (names or values) Quoting POSIX [1]: > Other [outside of of uppercase letters, digits, and...

Hi all, interesting thread. I know Lasse already mentioned that not freeing memory before exit is very common. For a more concrete example, this is the recommended behavior by the...

You can always use the system's `libc` implementation of `malloc` by running the following command: ``` $ make MALLOC=libc ``` Redis vendors jemalloc in `deps/jemalloc` and that is fairly common....

@moticless We have a RESP reference [here](https://redis.io/docs/latest/develop/reference/protocol-spec/) with it's source [here](https://github.com/redis/docs/blob/main/content/develop/reference/protocol-spec.md). Maybe it would be a better fit to have RDB files documented near that?

@Ecordonnier Your patch might be better than the current behavior; I haven't thought about it enough yet. However, I just wanted to clarify that the behavior of `SIGPIPE` should be...

While it looks correct in the case you list, it doesn't fix the handling of `SIGPIPE`. See the following example: ``` $ yes | head -n 1 y $ echo...

This looks incorrect. POSIX states [1]: > Signals set to the default action (SIG_DFL) in the calling process image shall be set to the default action in the new process...

I still don't think this is correct. The error should not be printed in this case, and the exit status of `yes` should not be zero: ``` $ ./target/debug/yes |...

Similar to #9554, it hits file descriptor limits: ``` $ mkdir -p `python3 -c 'print("a/" * 1024 * 16)'` $ ./target/debug/rm -rf a rm: cannot remove '[long file name snipped]':...

Hi, I'm one of the maintainers of Coreutils. Based on my reading of the referenced commit and your report, my guess is that all programs using the non-EVP APIs will...