GitHub user rusackas deleted a comment on the discussion: Roadmap to SQLAlchemy 2
Correction on the FAB theory from my last comment. Tested it directly in #42789 (draft, now closed), confirmed the registries actually do get unified with `model_class=` wired through, and the exact same CI failures happened anyway. So that wasn't it. Pulled real failure logs this time instead of the summary. `db.session.bind` is `None` outright at the point of failure, and a query right after a fixture sets up its data comes back empty. That's back to FSA 3.0's actual session-scoping change being the real suspect, not a registry mismatch. Going to dig into where the bind resolution actually breaks down before claiming a theory again. GitHub link: https://github.com/apache/superset/discussions/40273#discussioncomment-17902314 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
