Bug 128077 - WebKit Bot Watcher's Dashboard: Defer subsequent resource loads from access-restricted build bot when iteration fails to load with HTTP 401 status code
Summary: WebKit Bot Watcher's Dashboard: Defer subsequent resource loads from access-r...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Daniel Bates
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-02 12:20 PST by Daniel Bates
Modified: 2014-02-03 10:32 PST (History)
3 users (show)

See Also:


Attachments
Patch (7.24 KB, patch)
2014-02-02 12:21 PST, Daniel Bates
no flags Details | Formatted Diff | Diff
Patch (7.27 KB, patch)
2014-02-02 12:39 PST, Daniel Bates
no flags Details | Formatted Diff | Diff
Patch (8.10 KB, patch)
2014-02-03 10:00 PST, Daniel Bates
ap: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Bates 2014-02-02 12:20:14 PST
We should only prompt for HTTP credentials once per iteration load similar to what we do when we fetch the list of iterations (bug #127849). That is, if an HTTP 401 error occurs when we load an iteration we should notify the associated Buildbot object and update the associated queue view so that we prevent subsequent load attempt for other iterations (*) and show an "unauthorized" message on the dashboard, respectively.

(*) Such attempts would trigger an authentication dialog, which can be seen as annoying.
Comment 1 Daniel Bates 2014-02-02 12:21:46 PST
Created attachment 222932 [details]
Patch
Comment 2 Daniel Bates 2014-02-02 12:39:12 PST
Created attachment 222933 [details]
Patch

Rebased patch
Comment 3 Alexey Proskuryakov 2014-02-02 21:01:54 PST
Comment on attachment 222933 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=222933&action=review

> Tools/ChangeLog:12
> +        an iteration each time the update queue time fires until a person successfully authenticates. Instead
> +        we should update the authentication status of the build bot on receiving an HTTP 401 response code such
> +        that we defer subsequent requests to load the iteration when the queue update timer fires.

Isn't this too frequent? We load a lot of iterations.
Comment 4 Daniel Bates 2014-02-03 10:00:50 PST
Created attachment 222995 [details]
Patch
Comment 5 Alexey Proskuryakov 2014-02-03 10:16:22 PST
Comment on attachment 222995 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=222995&action=review

> Tools/ChangeLog:12
> +        HTTP credentials for an iteration so long as an earlier authentication request wasn't cancelled
> +        (i.e. failed with an HTTP 401 Unauthorized status code). Currently an authentication dialog will be
> +        presented for an iteration each time the update queue timer fires until a person successfully

I think that this would be easier to understand if it said "credentials for the buildbot" not "credentials for am iteration".
Comment 6 Daniel Bates 2014-02-03 10:29:25 PST
(In reply to comment #5)
> (From update of attachment 222995 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=222995&action=review
> 
> > Tools/ChangeLog:12
> > +        HTTP credentials for an iteration so long as an earlier authentication request wasn't cancelled
> > +        (i.e. failed with an HTTP 401 Unauthorized status code). Currently an authentication dialog will be
> > +        presented for an iteration each time the update queue timer fires until a person successfully
> 
> I think that this would be easier to understand if it said "credentials for the buildbot" not "credentials for am iteration".

Will change before landing.
Comment 7 Daniel Bates 2014-02-03 10:32:32 PST
Committed r163314: <http://trac.webkit.org/changeset/163314>