cargo-binstall stopped working

[jonathanpallant]

cargo-binstall stopped working

[NobodyXu]

@ryankurte They are using taiki-e/install-action, back then it's still using cargo-binstall v1.3.1

[NobodyXu]

It's probably a spurious failure, it doesn't provide me with enough information, but it would probably be ok if you retry it.

For the -musl target compilation failure, it's fixed in v1.4.1 and taiki-e/install-action would soon pick it up, so there's no need to change anything.

If it persists after taiki-e/install-action switches to v1.4.1, please let me know and I will investigate.

[jonathanpallant]

I retried it once. I'll try it a third time. Thank you for the quick response!

[NobodyXu]

@jonathanpallant I suspect it's GitHub that rate-limits your CI, the limit is usually reset hourly, so wait for 15m-30m and then it might succeed.

[passcod]

Yeah, it's definitely a 1.3.1 thing; 1.4.1 is in install-action @main but not yet in a released version

[jonathanpallant]

Which aspect do you think might be rate-limiting? We have a premium plan and I've never seen this before.

I bumped the version number for mdslides, and now it's downloading the binary OK. Do older binary packages stop working somehow?

[NobodyXu]

Which aspect do you think might be rate-limiting?

GitHub, but TBF their rate limit is quite loose considering the amount of traffic.

We have a premium plan and I've never seen this before.

I'd recommend you passing secrets.GITHUB_TOKEN to cargo-binstall via env (pass to taiki-e/install-action, it will pass to cargo-binstall).

The token wouldn't need any special permission and is used in a read-only way.

It would reduce possibility of such failure.

I bumped the version number for mdslides, and now it's downloading the binary OK. Do older binary packages stop working somehow?

Ni

[ryankurte]

this looks to me to be unrelated to github / like a regression due to changes to target detection for musl (same as #1420)?

[NobodyXu]

cc @jonathanpallant Does upgrading to latest cargo-binstall fix the issue for you?