"unexpected EOF during skip" error

[NobodyXu]

I keep getting:

+ cargo binstall --no-confirm [email protected]
 INFO resolve: Resolving package: 'cargo-watch@=8.4.0'
ERROR Fatal error:
  × For crate cargo-watch: I/O Error: unexpected EOF during skip
  ╰─▶ I/O Error: unexpected EOF during skip

when merging, they sometimes happen so I'm not sure whether it's a bug or just network failure.

Originally posted by @NobodyXu in #1186 (comment)

[NobodyXu]

This is spurious but annoying

[NobodyXu]

Ok so this actually comes from tar.

I was thinking about switching from tokio-tar back to it in #1200, but now it looks like a bad idea.
It will probably still fail just different errors, although it's better to return errors gracefully than panic.

[NobodyXu]

Both this issue and #1200 arises after I tried to speed the CI up by #1186 and #1188, so maybe we are sending http requests so fast that it is hitting the rate limit again.

@passcod Perhaps it is a good idea to apply more harsh rate limit in our binary?
Our default 10/1 (1 request each 10ms), changing it to 20/1 or 30/1 might fix the errors.

[passcod]

Can we set a harsher rate limit for CI only? We're going to have much stronger use than most consumers, it doesn't make sense to penalise the users for an issue that apparently only we're hitting.

[NobodyXu]

Can we set a harsher rate limit for CI only? We're going to have much stronger use than most consumers, it doesn't make sense to penalise the users for an issue that apparently only we're hitting.

I've opened #1201 and applied the harsh rate limit for CI only.

[NobodyXu]

Just realize that tokio-tar also has this "unexpected EOF during skip" error.

Fortunately tokio-tar v0.3.1 is out, let's try it out and see if it would fix the panic and this error.