exec: Execute batches before they get too long

[tavianator]

Fixes #410.

[tavianator]

Based on sharkdp/argmax#5.

Currently some tests fail because they expect the arguments to be sorted. That seems hard to do. If you're okay with it, I'll fix the tests to ignore the order.

[tavianator]

Hmm, all the runners are failing with

/home/runner/.cargo/bin/cargo clippy --locked --all-targets --all-features
    Updating crates.io index
error: the lock file /home/runner/work/fd/fd/Cargo.lock needs to be updated but --locked was passed to prevent this
Error: If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.
Error: The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

I thought it was due to the git dependency on argmax, but I switched to the released version and it's still failing. It works locally though:

$ cargo clippy --locked --all-targets --all-features
...
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s

Any ideas? I'll try cargo update I guess (no dice)

[tavianator]

I even tried running the exact workflow locally with https://github.com/nektos/act and it passed. Very confused.

[tavianator]

https://github.com/sharkdp/fd/runs/6596619198?check_suite_focus=true#step:5:1

I think I know what's happening: CI is testing the merge with master, not the branch itself. 🤦

[sharkdp]

Why was this removed? Because it could fail on a hypothetical platform with a very low argmax limit?

[sharkdp]

Ah no, because it makes assumptions about the sort order. Ok. I guess it's not really worth the effort. This path is already tested sufficiently in other tests.

[sharkdp]

Very nice ❤️

[sharkdp]

Really clear implementation. I also performed some successful local tests. No questions left 😄.

[tmccombs]

Sorry I didn't get to reviewing this sooner, but nice work @tavianator

[tavianator]

Thanks @tmccombs!