Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-6.0.rc1)
[email protected] Mon, 27 Apr 2026 02:05:30 -0700
| Newsgroups | org.yoctoproject.lists.yocto |
|---|---|
| Message-ID | <[email protected]> |
I'm also seeing the issue on my local build machine, building the imx-image-core image. Other users are encountering it as well: https://github.com/qualcomm-linux/meta-qcom/pull/2045/files I might be mistaken, but isn't the rate-limit mechanism from the PR linked by Richard only used for logging? https://github.com/rust-lang/simpleinfra/blob/2eaee4876c8bebbe00998b427a6c33012cddd910/terragrunt/modules/crates-io/fastly-webapp-ngwaf.tf#L5-L6 Also, per crates.io Data Access Policy, a user-agent should be present. https://crates.io/data-access#api I don't know if it's worth adding it to poky/bitbake/lib/bb/fetch2/crate.py since I can't find a rule that blocks request which are missing it. I'm afraid that the IP's encountering this issue might be manually blocked? https://github.com/rust-lang/simpleinfra/blob/2eaee4876c8bebbe00998b427a6c33012cddd910/terragrunt/modules/crates-io/fastly-webapp.tf#L11 Although I am wondering how my poor local machine's IP got so much atention.