davidzollo opened a new pull request, #11930:
URL: https://github.com/apache/seatunnel/pull/11930

   ### Purpose of this pull request
   
   Replacement for #11727 on an Apache-owned maintainer branch so current-head 
CI can run from the main repository.
   
   This republishes the current functional head of #11727 onto 
`apache/seatunnel` and keeps the full reviewed fix series that currently lands 
in only two files:
   
   - 
`seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/TaskExecutionService.java`
   - 
`seatunnel-engine/seatunnel-engine-server/src/test/java/org/apache/seatunnel/engine/server/TaskDeployStaleContextRaceTest.java`
   
   The republish carries over the stale-context hang fix plus the follow-up 
guards and regression coverage that were added during review on the contributor 
branch.
   
   ### Why this replacement PR exists
   
   The original open PR #11727 still points at the contributor fork. For this 
release batch we need the fix to run on an Apache-owned branch instead of 
continuing on a fork branch.
   
   ### Current-head CI note
   
   The latest failed CI on the original PR is not scoped to these changed 
files: the failing jobs are `Dead links`, Windows `unit-test`, and 
`all-connectors-it-7`, while the patch itself only changes 
`TaskExecutionService` and a dedicated engine regression test.
   
   ### Does this PR introduce a user-facing change?
   
   No normal-path behavior change is intended. It prevents the deployment path 
from hanging when the execution context disappears during startup and makes 
that failure settle instead of wedging the pipeline lifecycle.
   
   ### Validation
   
   Per the current SeaTunnel maintainer workflow for this batch, local 
validation was formatting-only:
   
   - `./mvnw spotless:apply -pl seatunnel-engine/seatunnel-engine-server -am 
-nsu`
   - `git diff --check`
   
   GitHub CI on this Apache-owned branch is the source of truth for compile, 
test, and runtime validation.
   


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