The GitHub Actions job "Required Checks" on texera.git/xinyuan-loop-feb has succeeded. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: 30ba48c39f21b08a88306de7eff12c67425fbe45 / Xinyuan Lin <[email protected]> refactor(amber): carry LoopStartId/LoopStartStateURI off State on the StateFrame envelope Review follow-up (r3285892274): user loop expressions exec against self.state, which the runtime also stuffed with loop bookkeeping -- a user writing e.g. `LoopStartId = ...` would silently clobber loop machinery. loop_counter was already moved off State; do the same for the LoopStart jump metadata. LoopStartId and LoopStartStateURI now ride the StateFrame envelope and are materialized as their own columns (parallel to content), exactly like loop_counter. The runtime owns them end to end: a LoopStart stamps them onto its output, the nested pass-through carries them, and the matching LoopEnd's jump reads them from the runtime (captured from the input frame) instead of executor.state -- so they never enter the user exec namespace. `table` (a user-facing input) and `output` (the runtime's capture variable) are intentionally left in scope and handled separately. Extends State to four columns and the ArrowUtils Tuple<->Arrow round-trip + materialization-reader tests to cover them. Co-Authored-By: Claude Opus 4.8 <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/26866705435 With regards, GitHub Actions via GitBox
