Open beyang opened 2 years ago
Added:
@beyang Updated Feedback on Slack doc
@beyang Updated Feedback on Slack doc
Note: Olaf is covering for TJ while OOO
You can communicate with the Mozilla representative that we have implemented infrastructure to sync all published crates from github.com/rust-lang/crates.io-index It will take some time to sync all crates so it's normal that many crates don't exist yet. We're starting by adding only the 5k most downloaded crates to see that everything works as expected. You can see the total list of synced crates with the query repo:^crates/ https://sourcegraph.com/search?q=context:global+repo:%5Ecrates/ 900 crates synced now. I think we have too restrictive rate limits causing the slow sync
That’s awesome! Let me know when it’s fully synced and I’ll write a patch to turn it on in cargo-vet I decided against a live demo for tomorrow’s presentation but I’ll include a slide with a Sourcegraph screenshot
We haven't switched to the CDN link yet because we didn't know about it when we first made the PR. We can switch to that soon. (Olaf is out of office this week) — TJ
there is also a WIP PR (that olaf will finish when he's back) that greatly reduces the number of requests that we make which should speed up package syncing greatly (not just for crates), so that will be a major improvement as well (CDN or not) — TJ
well right now we have it set to sync every 12 hours or so I think. We could probably reduce that time after we fix the other items (CDN + less requests) so that within a few hours of being pushed to the git repo, it could be online. I don't think it'd be worth doing more engineering time than that on it yet. How close to real time are we talking? The other option would be if you run lsif-rust or soon scip-rust on a repo, it will automatically add it's deps as soon as possible. So that would be another option to ensure that immediately new versions are available on sg — TJ
cc @beyang
We haven't switched to the CDN link yet because we didn't know about it when we first made the PR. We can switch to that soon.
Almost at the finish line, thanks for your patience :slightly_smiling_face:
Bobby đź‘Ť
@Bobby
Could you add ?ref=cargo-vet to the end of each URL? That way in rare cases your users are reporting an issue we can dig in faster.
Collab with Rust community and OpenSSF for Rust usage examples
Slack
#packages
09-30-2022
08-24-2022
08-15-2022
cargo update
before running cargo vet."08-11-2022
07-29-2022
07-28-2022
07-21-2022
07-20-2022
07-19-2022
07-14-2022
07-13-2022
0.13.1
07-12-2022
07-11-2022 Update
Success criteria