jinmengcheng commented on issue #29836: URL: https://github.com/apache/superset/issues/29836#issuecomment-2309431433
Hi @mistercrunch thanks for your reply and sorry reply late here due some personal businesses, I checked superset db current, it's pointing the head please see screenshot on "superset db current" and "superset db history" command line. Please also see my comments below for your 4 checklist may cause this issue: - some shenanigans happened on that db (like someone dropped the table) _This gonna not happen here, 😄_ - maybe someone messed with the migration precedence either in the repo or locally (say squeezing in that migration or forcing a SHA in the table) _Confirmed no one is doing migration except me_ - a false positive on the migration (?) like the create table failed but Alembic didn't know (?) I've never seen this before... _There is no error log on Alembic side, I have tested in a newly created DB(no tables), and directly run superset 4.0.2, user-favorite_tag table is created, as you mentioned you have never seen this before, I would consider this is very very tiny optopportunity to happen_ - your app isn't pointing to the same place as where you think the migration ran (?) I did not quite understand what this scenario, would you please kindly provide more details or take an example here?  -- 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]
