Community
Participate
Working Groups
I was cloning one of my github repositories and apparently used the wrong private key. But I couldn't read the error message because it disappeared immediately, since the authentication dialog came back up immediately. Note this is similar to the scenario in bug 347054 comment 2, except that in this case the failure is real. Ideally...when the user hasn't typed credentials in yet, there should be no failure reported. When there is a true auth failure, the error needs to be reported in a non-transient way.
Too bad you will never get informed about wrong private key. All we get from git is "Auth fail" and it doesn't make any difference whether private key is wrong, password, missing passphrase or missing user and password. I think I could try to keep the popup on top in this case but still all you would see would be "Auth fail". I'm not sure if this is helpful.
I think we could just ignore the Auth Failed when no credentials were provided i.e. all credentials fields were empty and treat the Auth Failed as a real failure just when any credentials were passed. I think this is what Susan meant.
Sure, I can try to do that. But it's still not very helpful that all you can see in the error is "Auth fail".
I meant both. If all we know is "auth fail" then that's all we can know. But the popup flashed so fast I couldn't read it that it said "auth fail." Also, as long as I have log full of fake "auth fail" errors when I haven't even tried to login, then I tend to distrust those errors. So hiding the ones that the user didn't trigger and then being able to see the auth fail when it really happens should be good enough.
Try it out now. I postponed popping out error for 10 milliseconds to allow caller to remove the operation. If operation is removed the popup is not displayed. I am also removing Auth fail when the credentials popup is shown, not when the operations is renewed, so if you close the login popup you have no record about "Auth fail".
*** Bug 347054 has been marked as a duplicate of this bug. ***
I was playing with it for two days and I don't have any annoying pupup and also my operations list doesn't contain "Auth fail" at all. I think the fix done its job, so I'm closing this bug. Susan, if you come across problems similar to described by this bug or Bug 347054, please reopen.
I don't recall seeing it recently either. thanks.
