-
Notifications
You must be signed in to change notification settings - Fork 113
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
Use UidNumber and GidNumber fields in User objects #1573
Conversation
de34f48
to
7aad73e
Compare
fabd746
to
0cb5c88
Compare
@sudo-sturbia majorly looks good, nice work! I'll test it since you don't have access to an EOS instance so there might be a delay in merging. We're working on getting EOS tests integrated in the CI so we should have that soon Meanwhile, please rebase and fix the failing integration tests. |
cb79532
to
999730a
Compare
@ishank011 Hi, I thought I'd let you know the latest updates: I looked at the integration tests and was able to find the errors, the changes are mainly in 999730a and e685753. As for the old commits, struct tags for |
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.
@sudo-sturbia LGTM! Good work on finding the issues with the integration tests. The LGTM tool is not that mature yet, so we do see intermittent build failures sometimes; we can ignore that. I'll test the changes tomorrow and merge.
That sounds great. Thank you! |
Update getUser to verify that uid and gid are not zero to avoid granting access to users by mistake.
Remove "opaque" map and use the correct value for "uid_number".
Update assertGetUserByClaimResponses integration test to verify that user is not nil.
f4d68cc
to
1db79ca
Compare
No description provided.