-
Notifications
You must be signed in to change notification settings - Fork 645
Owner invite doesn't work when username is specified with different casing #2081
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
Comments
I'm sorry this isn't working! I indeed don't see any invitations created by you for the hltas crate. I tried inviting someone to one of my crates in the web UI, so invitations works in general. I tried inviting I'm not sure why Can you try inviting them from the commandline, with We also have a bug that we're not reporting when and why invitations fail 😰 I looked in the logs for your requests and they all had status 200. |
Ah, it might be the case that I tried inviting with the capital first letter only before he has logged into crates.io for the first time, and only with the lowercase first letter afterwards. I tried inviting with the capital first letter again now. |
Looks like that worked! |
Great! I'm going to make this issue about the case problem and create some more issues for the other problems. Sorry this was such trouble, and thank you for reporting this so we can fix it! |
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to invite https://crates.io/users/matherunner to my crate https://crates.io/crates/hltas. I tried adding
Matherunner
,matherunner
as well as his email address, multiple times, always getting "An invite has been sent to matherunner". However, he never got any emails and his owner invites are empty.Implementation instructions
filter
to be case insensitive using thecrate::lower
function like this code does (I'm not sure why that code chooses to lowercase the provided name in Rust and then use the SQLcrate::lower
function on thegh_login
... I think both should be done with SQL in this case?) We have an index onlower(gh_login)
so this query will be fast.The text was updated successfully, but these errors were encountered: