-
Notifications
You must be signed in to change notification settings - Fork 13
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
Should guard better for user metadata being malformed/missing? #1085
Comments
…OMPLETE Underlying issue is somewhere in the logic/instructions so that locally created user lacks .metadata somehow, although it seems to be available within /admin interface among Users table for that user. So must be some glue missing etc. With this workaround it should still work ok, but would avoid crashing and due to INCOMPLETE I would expect that user lacking any super powers otherwise granted Workaround for #1085
with @djarecka we also got into the same error while trying to login using local user login but whenever neither first or last name of user were yet known to DB. Apparently if name is set (and I think I did it manually in I think that |
Yes, if you do not set name and last name for your user in edit actually, adding First Nam and Last Name doesn't solve the issue completely, this would give you new error on Looks like using @Yarik patch from #1086 AND adding First Name & Last Name gives me a way to finally log in. Although, still not able to create a new dataset: (you have to change your status to |
I'm able to reproduce this as well. It seems that the |
and I don't think that superuser can login into the archive, can he/she? |
@mvandenburgh could you please look into this issue again -- I decided to try local instance to develop but immediately ran into this issue |
The changes in #1113 will fix this. In the meantime, this README line from another PR describes a workaround for this - https://github.com/dandi/dandi-archive/pull/1809/files#diff-fc2a310fcfedfefb0046def697f932def80cbb1e78c689bc0af3c8eab3e33eceR10 |
Closed by #1113 |
🚀 Issue was released in |
Trying to get a local instance of API server + web UI for development.
I have DJANGO logged in in
/swagger
under my email/password. Tried to authorize and get a token butI went to
/admin
interface and added first and last name for my record in Users.and then now when I go to web UI at http://localhost:8085/ I get "Connection to server failed." and following traceback in console
suggesting that something about my user freaks server out. Confirmed by going to http://localhost:8000/api/users/me/ in the browser directly.
I think regardless of the problem with the user, server must not
500
The text was updated successfully, but these errors were encountered: