| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Thanks! Issue #10064 is now marked code review in progress and no longer open for pull requests, so this pull request holds the review for it and another one won't land on top of your work. If this pull request is abandoned, a maintainer can put open for pull requests back on #10064 to reopen it to others. |
Sorry, something went wrong.
There was a problem hiding this comment.
OK, this is sqla-tester setting up my work on behalf of zzzeek to try to get revision b9e5934 of this pull request into gerrit so we can run tests and reviews and stuff
Sorry, something went wrong.
|
New Gerrit review created for change b9e5934: https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/6991 |
Sorry, something went wrong.
|
Hi @zzzeek, I have addressed the PEP8 (line length / formatting) and PEP484 (typing in decl_base.py) issues flagged by the Gerrit verification pipeline:
The branch has been updated with commit c72f83b. Ready for Gerrit re-verification. Thank you! |
Sorry, something went wrong.
There was a problem hiding this comment.
Hi, this is sqla-tester and I see you've pinged me for review. However, user VimalN2005 is not authorized to initiate CI jobs. Please wait for a project member to do this!
Sorry, something went wrong.
There was a problem hiding this comment.
OK, this is sqla-tester setting up my work on behalf of zzzeek to try to get revision c72f83b of this pull request into gerrit so we can run tests and reviews and stuff
Sorry, something went wrong.
|
Patchset c72f83b added to existing Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/6991 |
Sorry, something went wrong.
There was a problem hiding this comment.
Federico Caselli (CaselIT) wrote:
Loiks fine. The sync teat script may require to be run
View this in Gerrit at https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/6991
Sorry, something went wrong.
Direct instantiation of unmapped classes (mixins or abstract base classes) using MappedAsDataclass is unsupported as ORM features and attributes cannot be resolved without concrete mapping. An SAWarning is now emitted when instantiating such classes directly. Concrete mapped subclasses remain unaffected and instantiate normally. Fixes: sqlalchemy#10064 Change-Id: I5875469671fce1f63e7e93776683e4ba9374c59b
|
I have addressed both review items:
Updated in commit 6031fac. Ready for review/CI run. Thank you! |
Sorry, something went wrong.
There was a problem hiding this comment.
Hi, this is sqla-tester and I see you've pinged me for review. However, user VimalN2005 is not authorized to initiate CI jobs. Please wait for a project member to do this!
Sorry, something went wrong.
There was a problem hiding this comment.
OK, this is sqla-tester setting up my work on behalf of zzzeek to try to get revision 6031fac of this pull request into gerrit so we can run tests and reviews and stuff
Sorry, something went wrong.
|
Patchset 6031fac added to existing Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/6991 |
Sorry, something went wrong.
There was a problem hiding this comment.
Federico Caselli (CaselIT) wrote:
code review left on gerrit
View this in Gerrit at https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/6991
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes
Fixes: #10064
Description
Direct instantiation of unmapped classes (mixins or abstract base classes) using MappedAsDataclass is unsupported as ORM features, column expressions, and relationship attributes cannot be resolved without a concrete mapping.
Per issue discussion and maintainer guidance:
Checklist