Bug 347054

Summary: [client][log] git log shows "auth failed" status while prompting me for credentials
Product: [ECD] Orion (Archived) Reporter: Susan McCourt <susan>
Component: GitAssignee: Malgorzata Janczarska <malgorzata.tomczyk>
Status: RESOLVED DUPLICATE QA Contact:
Severity: minor    
Priority: P3 CC: Mike_Wilson, simon_kaegi, Szymon.Brandys
Version: 0.2Keywords: polish
Target Milestone: 0.4   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
screenshot none

Description Susan McCourt CLA 2011-05-24 14:53:46 EDT
Created attachment 196476 [details]
screenshot

nitpicking.
When I get the credentials dialog during a fetch, the progress status tells me auth failed.  I think it should either say, "prompting for credentials" or just keep the previous status.

Since dojo fades the page this is not a big deal.  If it's easy to fix (like set the status only if the user cancels the dialog) then great.
Comment 1 Mike Wilson CLA 2011-06-01 16:18:14 EDT
I absolutely detest it when web UIs indicate some failure case when the true answer is "I don't know".
Comment 2 Susan McCourt CLA 2012-01-16 11:42:22 EST
I find this more annoying now than it used to be because the error causes the operations popup to flash on and off just before the credentials dialog comes up.
Comment 3 Susan McCourt CLA 2012-01-17 12:23:04 EST
another problem is that "auth fail" shows up in the operations history even though a failure never occurred from the users point of view.
Comment 4 Szymon Brandys CLA 2012-01-18 05:45:28 EST
Now all "auth fail" are removed from the ops view, when the operation is redone. There is only one more issue. When Git Fetch or other Git operations ask for credentials,  "auth fail" should be removed immediately when the credentials dialog is shown. At the moment "auth fails" is removed when Git op is redone with credentials (on clicking "ok" in the credential dialog).
Comment 5 Malgorzata Janczarska CLA 2012-01-24 08:13:03 EST
Let's do it together with bug 368852.

*** This bug has been marked as a duplicate of bug 368852 ***