Description
I hate to raise an issue based on what I consider to be mere speculation. However, unfortunately, "network issues" are very hard to pinpoint, so sometimes mere speculation is what we have. I have noticed that during my recent round of reviews for backtrace, which also offers serialization of a backtrace through serde, the network consistently chokes on this chain of errors:
warning: spurious network error (1 tries remaining): [28] Timeout was reached (Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds)
error: failed to get `syn` as a dependency of package `serde_derive v1.0.183`
... which satisfies dependency `serde_derive = "=1.0.183"` of package `serde v1.0.183`
... which satisfies dependency `serde = "^1.0"` of package `backtrace v0.3.69 (D:\a\backtrace-rs\backtrace-rs)`
... which satisfies path dependency `backtrace` of package `cpp_smoke_test v0.1.0 (D:\a\backtrace-rs\backtrace-rs\crates\cpp_smoke_test)`
It is always on this dependency chain. I have noticed random buggy network errors before, but they were always, well... fairly random. I have never noticed such a consistent error here before. Most crates are quite small after being gzipped for transfer, so I have to ask: Have you done something to significantly increase the amount of network traffic these dependencies incur?