I3eka commented on PR #43135:
URL: https://github.com/apache/superset/pull/43135#issuecomment-5659710433

   @rusackas, thanks — I checked the actual failing migration job rather than 
assuming all the red jobs were flakes. The branch is now synced to master 
`d9b0cb04`, head `77b7e45394`. A no-op merge revision joins the AI and upstream 
heads without rewriting the old migration; Alembic reports exactly one head. No 
deployed database was migrated.
   
   I also fixed the new duplicate-consumer cancellation-cleanup race: only the 
consumer that claimed the message clears Stop. The regression failed before the 
fix, and all 696 AI unit tests pass on the updated branch. Pre-commit passes 
for the changed compatibility/fix files. The full-branch pre-commit run still 
could not complete the frontend checks in this separate checkout (missing JS 
tool/workspace dependencies), so I am not claiming a green full suite; fresh CI 
is running.
   
   The new stale-worker, reload/resume and helper-directive threads, plus the 
earlier broker/history/model/TTL/checkpoint/API-cancellation concerns, are 
still open and are getting individual replies. In particular, master 
synchronization does not mean the #42805 fixes have landed. I also reviewed the 
updated Codecov report; the unmerged base's coverage is not waived by the 
focused regression. SIP/ownership follow-up: 
https://github.com/apache/superset/pull/42805#issuecomment-5659710194.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to