DanielLeens commented on PR #12218: URL: https://github.com/apache/seatunnel/pull/12218#issuecomment-6338339559
Thanks @SEZ9 and @Rangsh. Agreed on keeping the registry failure and the cancel-versus-worker-loss race separate from this deploy rollback fix. There is no new source request from my side. The cancellation correction #12311 is still open, so syncing current `dev` alone is not a demonstrated cure for that race. A targeted retry of the registry-failed Kafka job after registry availability recovers is useful; please retain the new job link if an executed assertion then fails. CI on the final head and a write-capable maintainer approval remain the merge gates. I have not rerun any workflow or performed another full code review in this follow-up. Status evidence: head `35f5a2fcf7c9ad52f25f07d299a2f918925ebd19`, base `dev`, compare `diverged`, ahead 11, behind 80; GitHub mergeable state `blocked`. -- 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]
