$ the-wire · showcase
docs.rs targets SQLite race conditions, crates.io drops legacy Prometheus metrics
By RepoJournal · Filed · About Rust · Composed from the cited sources · methodology
Two migrations land in the Rust infrastructure: docs.rs is chasing down the race between cache cleanup and archive-index repair, and crates.io finishes moving its metrics story onto OpenTelemetry.
Reduce missing/corrupt SQLite archive-index errors caused by overlapping cache cleanup and repair rust-lang/docs.rs
syphar's PR attacks the overlapping cache cleanup and repair that produce 'error returned from database: (code: 14) unable to open database file' and flaky tests, noting the storage engine only reports to Sentry after 5 retries and that the fixes are "more or less guesses about where these race conditions happen." Treat it as a mitigation in progress, not a closed bug.
metrics: Remove legacy Prometheus metrics rust-lang/crates.io
OpenTelemetry now covers the server and worker metrics that Prometheus used to expose, so the private endpoint, legacy instruments, endpoint configuration, and the unused Prometheus dependency all come out. The database snapshot the OpenTelemetry collector reads stays in place, so existing dashboards built on that source keep working.
monitor: Remove obsolete spam crate check (#14745) rust-lang/crates.io
The monitor's spam crate check is gone: Turbo87 says the setting has gone unused for years and the behavior can live in Datadog instead of application code. Less configuration to carry in the app itself.
Rollup merge of #163080 - cyrgani:builtin-macros-5, r=nnethercote rust-lang/rust
Part 5 of the rustc_builtin_macros cleanup removes the "mini" Path, the nonselflike_args, and most uses of type_ident, and comes with some perf gains. Followup to the earlier cleanup pass.
Use span context for enclosing item(s) of unmet bound rust-lang/rust
estebank's diagnostic change points at the item that introduced an unmet bound, and at the enclosing trait or impl for associated items, without a span label. In the thin tail: miri turns off rust-analyzer diagnostics in its VSCode settings because RA reports many false positives, and docs.rs bumps its opentelemetry monorepo to 0.33.0 with matching resource detectors.
