DanielLeens commented on PR #10551:
URL: https://github.com/apache/seatunnel/pull/10551#issuecomment-4968420520

   Rechecked the current head `62b84bb4f2c8` against the latest `dev` after the 
CI / merge-gate fact changed.
   
   ## Runtime path rechecked
   ```text
   state transition on the active master / worker
     -> PhysicalPlan.updateJobState(...) [PhysicalPlan.java:308-330]
     -> SubPlan.updatePipelineState(...) [SubPlan.java:345-406]
     -> PhysicalVertex.updateTaskState(...) [PhysicalVertex.java:351-417]
         -> when the distributed state entry is missing
             -> fall back to local curr* state
             -> recreate the map entry with the target state
   
   downstream readers that still consume the distributed map directly
     -> JobHistoryService.toJobStateMapper(...) [JobHistoryService.java:257-306]
         -> reads runningJobStateIMap for job / pipeline / task states
     -> CoordinatorService.restoreJobFromMasterActiveSwitch(...) 
[CoordinatorService.java:506-521]
         -> still branches on the distributed job-state entry directly
   ```
   
   ## Merge conclusion
   ### Conclusion: source blocker cleared from Daniel's side; sync latest `dev` 
and rerun CI first
   
   1. Blocking items
   - None reopened from Daniel's source review on this unchanged head.
   - This branch is behind upstream (`compare status: diverged`, `ahead_by=3`, 
`behind_by=149`), and the current failing gate is `FAILURE gate: Build`: 
https://github.com/apache/seatunnel/runs/86810034333
   
   2. Lowest-cost next step
   - Please sync with the latest `dev` and rerun the failing gate first.
   - If it still fails on the updated head, I can help narrow down the new 
failure from there.
   
   Daniel only has `READ` permission on this repository, so a write-capable 
maintainer may still need to handle the final approval / dismissal step once 
the gate is clear.
   


-- 
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]

Reply via email to