SEZ9 commented on PR #12209:
URL: https://github.com/apache/seatunnel/pull/12209#issuecomment-6817394911

   Thanks @88fantasy for the summary.
   
   The follow-up plan sounds good: F4 (only advance the heartbeat throttle 
timestamp after a successful emit, or reset it on failure) and a typed config 
holder for the lineage options replacing the raw map in `EngineConfig` can go 
into a single tracked issue after merge, and the docs polish can live in the 
same issue. No need to open it before merge.
   
   On the current head `2e236b4b`: compared with `d4cddb0b`, the only change is 
the merge of the latest `dev`, and the PR's net diff against `dev` is 
unchanged. No source blocker is open.
   
   The remaining gate is CI: there is still no `Build` run for this head. Could 
you check that GitHub Actions is enabled on your fork and trigger the `Build` 
workflow manually on this branch? I'll re-confirm as soon as a green run exists.
   
   <!-- streview-comment:2286 -->


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