| Filename | Latest commit message | Latest commit date |
|---|---|---|
f6ce73237a
Some checks failed
congrats.yml / fix: finish the rand 0.10 migration across test-only targets (push) Failing after 0s
deploy_docs.yml / fix: finish the rand 0.10 migration across test-only targets (push) Failing after 0s
deploy_nightly_docs.yml / fix: finish the rand 0.10 migration across test-only targets (push) Failing after 0s
extension_bump.yml / fix: finish the rand 0.10 migration across test-only targets (push) Failing after 0s
run_tests / orchestrate (push) Has been cancelled
run_tests / check_style (push) Has been cancelled
run_tests / clippy_windows (push) Has been cancelled
run_tests / clippy_linux (push) Has been cancelled
run_tests / clippy_mac (push) Has been cancelled
run_tests / clippy_mac_x86_64 (push) Has been cancelled
run_tests / run_tests_windows (push) Has been cancelled
run_tests / run_tests_linux (push) Has been cancelled
run_tests / run_tests_mac (push) Has been cancelled
run_tests / miri_scheduler (push) Has been cancelled
run_tests / doctests (push) Has been cancelled
run_tests / check_workspace_binaries (push) Has been cancelled
run_tests / build_visual_tests_binary (push) Has been cancelled
run_tests / check_wasm (push) Has been cancelled
run_tests / check_dependencies (push) Has been cancelled
run_tests / check_docs (push) Has been cancelled
run_tests / check_licenses (push) Has been cancelled
run_tests / check_scripts (push) Has been cancelled
run_tests / check_postgres_and_protobuf_migrations (push) Has been cancelled
run_tests / tests_pass (push) Has been cancelled
The 0.10 upgrade was completed on the shipping paths but left twelve crates uncompilable in `#[cfg(test)]`, `test-support`, bench, and example code. Release builds never compile those targets, so every platform shipped green while `cargo test --workspace` could not build at all — `cargo check --workspace --all-targets` is the gate that catches this, and it now passes with zero errors. Three distinct 0.10 changes were involved. `random_range`, `random_bool`, and `fill` moved from `Rng` to the new blanket-implemented `RngExt`, so the fix is an import at the cfg gate matching the surrounding code; where that made the old `Rng` import dead it is dropped. `RngCore` was renamed `Rng`, which is where `next_u32` now lives. `StdRng` lost `Clone`, so the two randomized collaboration tests derive the network's generator with `StdRng::from_rng` instead — still reproducible per seed, and independent rather than an identical stream as cloning produced. Grepping for the import does not find these reliably: several files carry a function-local `use rand::prelude::*` covering some call sites and not others, and a broken foundation crate masks the next layer, so this was iterated against the compiler through text, git, language, multi_buffer, git_graph, and editor. Restoring the git crate's test target exposed two tests that had been invisible rather than passing: the Zed to Joule rebrand rewrote a blame golden file and a branch-parsing expectation without rewriting the fixtures they are derived from. The fixtures are aligned with the rebranded expectations. Co-Authored-By: Claude Opus 4.8 <[email protected]> |
||
| .. | ||
| golden | ||
| blame_incremental_complex | ||
| blame_incremental_not_committed | ||
| blame_incremental_simple | ||