carloea2 opened a new pull request, #8583: URL: https://github.com/apache/texera/pull/8583
### What changes were proposed in this PR? Add the core runtime for generated Python workflow drivers: a local variable heap, explicit input/output boundaries, field ownership checks, and a fresh global-binding namespace per execution. Invalid boundary IDs and incomplete output contracts fail explicitly. The tuple-operator adapter and native binding helpers follow in PR 3B. ### Any related issues, documentation, discussions? Related to apache/texera#8319 (PR 3A). Depends on apache/texera#8433; keep this PR in draft until the codec prerequisite merges and this branch is rebased. The runtime slice adds 611 lines across two files (303 implementation, 308 tests). The current diff also includes the codec prerequisite: 938 additions across five files. ### How was this PR tested? From `amber/`, Python 3.12: ```text python -m pytest src/test/python/pytexera/workflow -m "not integration" -q -p no:cacheprovider --cov=pytexera.workflow.runtime --cov-branch --cov-report=term-missing python -m ruff check src/main/python/pytexera/workflow src/test/python/pytexera/workflow python -m ruff format --check src/main/python/pytexera/workflow src/test/python/pytexera/workflow ``` 54 tests passed; core runtime statement and branch coverage is 100%. Lint and formatting passed. Regression tests reproduced acceptance of non-string boundary IDs before the validation fix. Coverage includes missing/duplicate boundaries, ownership conflicts, absent bindings, malformed payload recovery, and execution namespace isolation. Local verification used an existing generated-protobuf directory on a secondary Python path; the runtime and codec were loaded from this release checkout. The coverage run emitted a NumPy reload warning. Full integration and cross-version results will come from CI. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: OpenAI Codex (GPT-6) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
