aawsome
aawsome
Of course, we can either add an option to opt-out the sigpipe handling or maybe just handle it in very special situations (like the the `backup -` case). I however...
@raggi I must say I cannot fully judge the resulting signals given on different situations on various operation systems. However, in meantime we support the `stdin-command` option which IMO should...
I manually rebased to newest main. @simonsan Can you please have a look at this PR? I think that a test on Windows is very much necessary here, but I...
waiting for https://github.com/BurntSushi/ripgrep/commit/79f5a5a66e68aa50ef9f63ded777e640d345df5e to be released in `globset`.
@simonsan Can you have a look at this PR? The tests currently fails as we'd need to adapt the CI pipelines to use the `ci` feature instead of all features....
While I agree that we might want to migrate from `log` to `tracing`, I actually would do so when we have decided for the architecture we are using to run...
> Hmm, I don't understand, why would that be related to an architectural decision? `tracing` is essential in `async/parallelized` contexts, for sure. But we can already profit a lot from...
just one thing: Did you see the tests in `crates/core/tests/command_input.rs`?
@tarcieri sure, here it is: ```Rust assert!(scrypt::Params::new(18, 1, 5, 32).is_ok()) ``` (currently, this fails due to the check on `log_n`)
I can provide a PR removing that check on log_n, if wanted.