mengw15 opened a new pull request, #8621: URL: https://github.com/apache/texera/pull/8621
### What changes were proposed in this PR? Backport of #8432 to `release/v1.3`: a clean cherry-pick of its squash commit, no adaptations — the backport commit reuses the squash message and author, as the automated fast path would. See #8432 for the change itself (channel markers bind to the port resolved by their control handler instead of the last data tuple's port, and invalid markers are rejected before entering the executor). Opened manually by the v1.3 release manager: the automated fast path cherry-picked this cleanly and then pushed it straight to `release/v1.3`, where the Merge Queue ruleset rejected the push (`GH013`, [run 35187408300](https://github.com/apache/texera/actions/runs/35187408300)). The Actions-app bypass meant to unblock that path (#8379) was never created — asfyaml rejects an `Integration` bypass actor — and the failing job's notification 403s for want of `pull-requests: write`, so the loss left neither a backport PR nor a comment on #8432. See #8377. Source: 471e53cfc1d5f96748a7ec6b7563561239229e5e ### Any related issues, documentation, discussions? Backport of #8432. Related to #8319. ### How was this PR tested? The change is identical to #8432, which carries 235 lines of new pytest coverage (`test_channel_marker_handlers.py`, `test_data_processor.py`, `test_main_loop.py`); the backport tree is verified byte-identical to cherry-picking the squash commit onto `release/v1.3`, and release-branch CI runs the full matrix on this PR. The two branch-level blockers that used to make pyamber jobs red here are already merged: #8549 (LICENSE-binary-python drift) and #8550 (RustFS as the default object store). ### Was this PR authored or co-authored using generative AI tooling? Yes. Generated-by: Claude Code (claude-opus-5) -- 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]
