Repository navigation
Conversation
…t its context The rows store's write worker had a fixed 1 GiB permit, and a save whose new bytes passed it was skipped with StagingFull. At about 65 KB a token, a 27B conversation whose first save or post-compaction prompt held more than about 13K new tokens was never written, nor any later save of it. rows.Options.longest sizes the permit to one state of that many tokens with no rows on disk (coldCharge), never under the 1 GiB floor nor past the RAM store's budget; the 27B host passes its --context. Other hosts keep 1 GiB.
zig/build/cuda.zig was at the 600-line limit, so every new CUDA hook had to move lines out first. Two contiguous groups of host-test registrations from hostTests move verbatim, each behind one pub fn called once from where the group stood, so steps and dependencies register in the same order: - cuda_contract_host.zig steps(): the CPU contract references (Flash Next writeback, utility, row-best and QSA; cuda_row_contracts and cuda_window_host hooks; FP64 quant and projection fixtures). - cuda_server_host.zig steps(): the HTTP server's host tests over server_tests, through test-server-cpu and the off-macOS goldens and fuzz step; it returns template and server_tests for the tests after it. All 134 moved lines and the golden.zig import are byte-identical; the new parameters keep the old variable names. cuda.zig: 600 -> 467 lines. zig build -l is unchanged (empty diff) by default, with -Dhip=true and for x86_64/aarch64 Linux and x86_64 Windows targets.
…n, as step5-filter is Linux's
Owner
Author
|
Stopped at #2388. |
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.
CI for a landing train: #2388 #2420 #2163 stacked on main in that order. Nothing merges from this PR: each PR above lands on its own once this tip is green, and this PR is then closed.