Report measured host RAM capacity progress - #267
Merged
Conversation
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.
Implements python-gen-worker tracker #548.
Host-RAM admission failures now carry typed required/observed byte counts and a process-scoped generation. After an explicit owner/pin release, the worker reports
HOST_CAPACITY_PROGRESSonly when newly measured headroom actually increases enough to satisfy the remembered requirement. No elapsed-time retry, lifecycle timeout, environment knob, or broad CUDA cache flush is introduced.Reconnect handling retains active failures and only undelivered satisfying progress. Its bounded queue preserves active-failure priority, replaces stale same-ref generations, fences blocked stale full-state producers, and clears progress on the same successful stream-write boundary already used for durable results. Old protocol-v3 consumers continue to parse failures and ignore the additive progress enum/fields.
Validation:
58548bb87e4d616241cae97acd77ea7cfc8d9ad2