fix(build): restore deleted extract/build.rs and align stale test/exa…#46
Open
deem0n wants to merge 1 commit intochrishayuk:mainfrom
Open
fix(build): restore deleted extract/build.rs and align stale test/exa…#46deem0n wants to merge 1 commit intochrishayuk:mainfrom
deem0n wants to merge 1 commit intochrishayuk:mainfrom
Conversation
…mple initializers The Virtual Experts merge (PR chrishayuk#45) left `main` unable to build: 1. `crates/larql-vindex/src/extract/build.rs` was deleted but `extract/mod.rs` still declares `pub mod build;` and re-exports `build_vindex` / `build_vindex_resume`, which are still called from `larql-cli`, `larql-lql`, the vindex tests, and the `demo_features` example. The roadmap (vindex M8) plans to split this file into `build/{mod,...}.rs`, but that refactor was never finished. Restore the file from `d3a8bc6^` so the workspace compiles again; the planned split can land separately. 2. New required fields had been added to several public structs but a number of test fixtures and examples were not updated, so `cargo build --features metal` and `cargo test --workspace` failed with E0063 / E0308: - `FullPipelineLayer.ffn_is_remote` — added to 6 `larql-compute` examples (`compare_decode`, `compare_formats`, `compare_ollama`, `compare_pipeline`, `demo_architecture`, `diag_decode_pipeline`). - `LoadVindexOptions.moe_remote` — added to `bench_expert_server` and `openai_demo` examples. - `LoadedModel.{unit_filter, moe_remote}` plus the `metal-experts`-conditional `metal_backend` / `moe_scratches` / `metal_ffn_layer_bufs` fields, and the `weights` field's new `OnceLock<RwLock<ModelWeights>>` wrapper — fixed in `tests/common/mod.rs`, `tests/test_expert_endpoint.rs`, `tests/test_http_full_routes.rs`, `tests/test_unit_band_utils.rs`, `tests/test_unit_state.rs`. - `VindexConfig.{fp4, ffn_layout}` and `ModelWeights.skipped_tensors` in `tests/test_expert_endpoint.rs`. - `MoeLayerWeights.expert_data_format` plus per-expert byte-slice layout (`Vec<&[u8]>` instead of a single `&[u8]`) in the same test's `local_output` helper. Result: workspace builds clean with `--features metal`, and 3,481 tests run (the remaining failures are runtime numerical-correctness issues in Metal kernels — unrelated to this commit, and the reason this branch exists). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Virtual Experts merge (PR #45) left
mainunable to build:crates/larql-vindex/src/extract/build.rswas deleted butextract/mod.rsstill declarespub mod build;and re-exportsbuild_vindex/build_vindex_resume, which are still called fromlarql-cli,larql-lql, the vindex tests, and thedemo_featuresexample. The roadmap (vindex M8) plans to split this file intobuild/{mod,...}.rs, but that refactor was never finished. Restore the file fromd3a8bc6^so the workspace compiles again; the planned split can land separately.New required fields had been added to several public structs but a number of test fixtures and examples were not updated, so
cargo build --features metalandcargo test --workspacefailed with E0063 / E0308:FullPipelineLayer.ffn_is_remote— added to 6larql-computeexamples (compare_decode,compare_formats,compare_ollama,compare_pipeline,demo_architecture,diag_decode_pipeline).LoadVindexOptions.moe_remote— added tobench_expert_serverandopenai_demoexamples.LoadedModel.{unit_filter, moe_remote}plus themetal-experts-conditionalmetal_backend/moe_scratches/metal_ffn_layer_bufsfields, and theweightsfield's newOnceLock<RwLock<ModelWeights>>wrapper — fixed intests/common/mod.rs,tests/test_expert_endpoint.rs,tests/test_http_full_routes.rs,tests/test_unit_band_utils.rs,tests/test_unit_state.rs.VindexConfig.{fp4, ffn_layout}andModelWeights.skipped_tensorsintests/test_expert_endpoint.rs.MoeLayerWeights.expert_data_formatplus per-expert byte-slice layout (Vec<&[u8]>instead of a single&[u8]) in the same test'slocal_outputhelper.Result: workspace builds clean with
--features metal, and 3,481 tests run (the remaining failures are runtime numerical-correctness issues in Metal kernels — unrelated to this commit, and the reason this branch exists).