New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 776717 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 770327
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

500 Server Error after signing in to codereview.chromium,org

Reported by bgib...@htps.us, Oct 20 2017

Issue description

Chrome Version       :  62.0.3202.62 (Official Build) (64-bit)

What steps will reproduce the problem?
1-Visit https://codereview.chromium.org/2676673002/
2-Click Sign In https://www.google.com/accounts/ServiceLogin?service=ah&passive=false&continue=https://appengine.google.com/_ah/conflogin%3Fcontinue%3Dhttps://codereview.chromium.org/2676673002/


What is the expected result?
Be able to view issue as identified user, and add comments

What happens instead?
After authenticating, all this URL return is "500 Server Error"

Troubleshooting steps:

Incognito, enterprise account, gmail account, root url.....same result

 
Cc: -andyb...@chromium.org
Cc: susanjuniab@chromium.org
Labels: M-64 Needs-Triage-M62 OS-Linux OS-Mac OS-Windows Pri-2 Type-Bug
Status: Untriaged (was: Unconfirmed)
bgibson@ Thanks for the issue.

Able to reproduce the issue on Windows 7, Mac OS 10.12.6 and Ubuntu 14.04 using the latest Stable 62.0.3202.62 and Canary 64.0.3250.0.
This is a Non-Regression issue as this issue is observed from M50 chrome builds.
Attached is the screen cast for reference.

Hence marking this as 'Untriaged' for further updates from Dev.

Thanks.
776717.webm
3.5 MB View Download
Mergedinto: 770327
Status: Duplicate (was: Untriaged)
Rietveld has been turned down, no database-modifying actions are possible anymore. I can visit that review and sign in without any trouble now.

Your email address doesn't show up in autocomplete, so it appears that you haven't signed in previously. In that case, it is not surprising that signing in results in a 500 (since when new users sign in, the app tries to create a database entry for them), and I'm working on fixing all of these corner cases still. That said, signing in will not give you any additional benefits now that the app is in a fully static state, so don't worry about this too much.

Sign in to add a comment