-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Unable to login and missing keypairs when a user does not have any project #1360
base: main
Are you sure you want to change the base?
Conversation
sa.join(keypairs, users, keypairs.c.user == users.c.uuid, isouter=True) | ||
.join( | ||
association_groups_users, | ||
users.c.uuid == association_groups_users.c.user_id, | ||
isouter=True, | ||
) | ||
.join(groups, association_groups_users.c.group_id == groups.c.id, isouter=True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should never OUTER JOIN three tables in any case.
Keypair
graphene query mismatch between count and sliceKeyPair
GraphQL query mismatch between count and slice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another issue to look together: if there exists a user who does not belong to any project, all user's login is blocked due to a query error. |
KeyPair
GraphQL query mismatch between count and slice
This should be resoled before shipping 23.09.5. |
…and-slice' into fix/keypair-query-correct-count-and-slice
@achimnol I resolved the issue that unable to fetch keypairs whose user is not associate with any project. ![]() |
follow-up #1022
If a user is not associated with any group (project), the user's keypairs are not included in the
KeyPairList
query result, with a mismatch ofcount
andslice
resolvers.If one or more user is not associated with any group (project), all users cannot login to the web UI. At least, the login error should be confined to the specific user, without affecting other users with proper project memberships.
Suggestion
How about deprecating
projects
fields of Keypairs?I made a commit to test it
Checklist: (if applicable)