New issue
Advanced search Search tips

Issue 821728 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Make error message in the toast more descriptive (should mention that only @google.com users can use Debug button)

Project Member Reported by serg...@chromium.org, Mar 14 2018

Issue description

...even though I can. Probably because I am a trooper. Need to document which group the user should be in to be able to use it. Michael, can you please post an error message that you've received here?

This affected issue 819237.
 

Comment 1 by mar...@chromium.org, Mar 14 2018

The user has to login with a @google.com
Summary: Make error message in the toast more descriptive (should mention that only @google.com users can use Debug button) (was: mvstanton@ is not able to use Debug button on swarming)
Thanks for explaining. I've just tried this with a @chromium.org account and got a toast "Request failed. Reason: [object Object]". Would be nice to have a more descriptive error message.

Comment 3 by mar...@chromium.org, Mar 14 2018

Labels: Type-Bug
Owner: kjlubick@chromium.org
Status: Assigned (was: Untriaged)
-> Kevin since people may try it, not understand why it failed, just give up and move on. So we don't have (much) signal on how many tried and failed to.

The error message should hint that maybe another account may have access, albeit we can't state which. :/
Alternatively, can we grant the right to trigger builds to Googler @chromium.org account? We have a group for that in https://chrome-infra-auth.appspot.com/auth/groups/google/googlers@chromium.org.

Comment 5 by mar...@chromium.org, Mar 14 2018

That's a separate task, focusing this bug on the UI.
Project Member

Comment 7 by bugdroid1@chromium.org, Mar 16 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/c614e81f06c0c56fc76ed338933a8d423ae7804f

commit c614e81f06c0c56fc76ed338933a8d423ae7804f
Author: Sergiy Byelozyorov <sergiyb@google.com>
Date: Fri Mar 16 10:44:07 2018

Comment 8 by kjlubick@google.com, Mar 16 2018

Cc: kjlubick@chromium.org vadimsh@chromium.org
 Issue 814577  has been merged into this issue.

Comment 9 by kjlubick@google.com, Mar 16 2018

Status: Fixed (was: Assigned)
The better error handling/message is now live.

Sign in to add a comment