Crates.io Dependents upstream timeouts

[jNullj]

Are you experiencing an issue with...

shields.io

🐞 Description

The Crates.io Dependents badge will frequently fail on first try.
After a small debug i noticed the following:

1. some requests to upstream take over 8s to reply.
2. second request to the same time is much quicker (i got 600ms for a crate that hit 5.5s at https://crates.io/api/v1/crates/proc-macro2/reverse_dependencies, our example, tokio takes over 10s the first try and 3.5 on the second try https://crates.io/api/v1/crates/tokio/reverse_dependencies).
3. we fail daily tests

My guess is that the second request is quicker due to some kind of cache.

🔗 Link to the badge

https://img.shields.io/crates/dependents/tokio

💡 Possible Solution

seems like upstream issue and there is little we can do about this

[jNullj]

created a new issue upstream

[jNullj]

We got a response from the devs, this is an open issue (see also rust-lang/crates.io#11834).
We can (and encouraged by upstream) to increase our cache time for this badge.

How i think we should move forward:

1. Increase timeout for test, as we have this issue open now and we want to test functionality.
2. Add a comment about this potential issue on the badge for users to know of.
3. Increase cache time to reduce the number of refreshes and reduce strain from upstream.

I subscribed to the upstream issue in case this gets resolved.

[Turbo87]

1. Increase timeout for test, as we have this issue open now and we want to test functionality.

if you want to test this, I'd suggest to select a somewhat unpopular crate with very few reverse dependencies. the query time scales with the number of reverse dependencies, so if you use an unpopular one, the test should be faster.

[PyvesB]

Thanks for looking into this issue, @jNullj !