Repository navigation
Conversation
This branch has not been deployed
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.
Runner artifact bytes currently depend on retained local files and complete archive bundles. This adds a scoped object-storage publication path using native PyFly ECM providers, independent PostgreSQL chunk rows, constant-size manifest roots, keyset reads and explicit reconciliation after uncertain writes. Raw-file upload, lease-checked streaming read and private atomic restore are wired into the controller and artifact producer/consumer paths. Existing local bindings remain unchanged unless explicitly configured.
Validation: 60 host cases passed (one existing process-dependent legacy case excluded under the effects-denial guard); two dedicated PostgreSQL cases passed in 5.37s using a non-superuser application role, including native DI/ASGI upload, concurrent publication, paged restore and lost-reply readback. The owned fixture stopped and temporary credentials were removed. Full mypy checked 414 source files; Ruff/format passed; strict documentation, 10 docs units and 73 pages/10,359 local links passed. No models, Docker workloads, cloud services or Original data were used.
This is a draft integration slice. Live provider acceptance, released native GCS support, Kubernetes scheduling, a reference-native Docker carrier, setup UI, catalog-to-file content reads and production retention remain open. The legacy carrier still buffers archives and RunnerPoolWorker still depends on its admitted central workspace. No enterprise-scale acceptance or migration is claimed.