Tristan P. 9f714e62cb [umkdir][tests] get umask instead of assuming it (#14046) ... # Description Contributors to this projects will have a test failure if their `umask` is not set to `0022`. Apparently on Debian (at least on my install), it is set to `0002` which makes my test fail. While `0022` is safer than the value I have, I want to reduce the amount if issue new contributors could have. I am making this test not assuming anything and instead, reading the user umask. # Related discussion I see that the `umask` command implementation has been discussed in #12256 . We could use this and enforce a umask for tests who rely on this. I believe however (let me know what you think) that hard coded values are harder to read in the test. # User-Facing Changes N/A # Tests + Formatting All green on my side after this MR 👍 # After Submitting Documentation is not impacted --------- Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>		2024-10-11 14:13:42 +02:00
..
commands	[umkdir][tests] get umask instead of assuming it (#14046)	2024-10-11 14:13:42 +02:00
format_conversions	Make the subcommands (from {csv, tsv, ssv}) 0-based for consistency (#13209)	2024-06-26 17:51:47 -05:00
main.rs	Rework sorting and add cell path and closure comparators to sort-by (#13154)	2024-10-09 19:18:16 -07:00
sort_utils.rs	Rework sorting and add cell path and closure comparators to sort-by (#13154)	2024-10-09 19:18:16 -07:00