DanielLeens commented on PR #12578: URL: https://github.com/apache/seatunnel/pull/12578#issuecomment-6338319410
Thanks @SEZ9; that matches my source-level conclusion. The cache invalidation contract and its documented escape hatches do not need another source change here. The current failed check is still [Notify test workflow](https://github.com/apache/seatunnel/actions/runs/38787676286/job/116603788523), with no attached Build result for this SHA. I should narrow my earlier sync suggestion: branch drift does not establish a remedy for the reported GitHub API 500. A maintainer can retry the failed notification after the service error clears; alternatively, please start Build on this exact branch in the fork Actions tab and link the run so its result can be checked. Please do not add a source patch or an empty commit just to chase that service error. A successful required Build and write-capable maintainer approval are still needed. Status evidence: head `ef53a70c6f72f5f6ae7c31fcc57b541eb3c849f3`, base `dev`, compare `diverged`, ahead 3, behind 56; 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]
