|
|
Created:
4 years, 2 months ago by Charlie Harrison Modified:
4 years, 2 months ago CC:
chromium-reviews, alemate+watch_chromium.org, achuith+watch_chromium.org, vabr+watchlistlogin_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionSimplify origin logic in login_handler
This code had logic for continuing execution after a NOTREACHED(),
which is against the style guide. With this removed the code is much
simpler.
Committed: https://crrev.com/e406acaf0d5e19c1f13161f0e2c7d552329dfebe
Cr-Commit-Position: refs/heads/master@{#424840}
Patch Set 1 #
Depends on Patchset: Messages
Total messages: 19 (12 generated)
The CQ bit was checked by csharrison@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
csharrison@chromium.org changed reviewers: + asanka@chromium.org
asanka, is this reasonable? Should we CHECK this condition? I tried tracing the code to see if this will ever be false and didn't see anything obvious.
Description was changed from ========== Simplify origin logic in login_handler BUG= ========== to ========== Simplify origin logic in login_handler This code had logic for continuing execution after a NOTREACHED(), which is against the style guide. With this removed the code is much simpler. ==========
On 2016/10/05 at 11:58:22, csharrison wrote: > asanka, is this reasonable? Should we CHECK this condition? I tried tracing the code to see if this will ever be false and didn't see anything obvious. Yeah, a DCHECK is fine to leave in. Looks like the logic was left over from an old bug hunt. LGTM
csharrison@chromium.org changed reviewers: + vabr@chromium.org
Thanks, yeah that was my take as well. I was just nervous that there might be security implications because this is login code. +vabr for OWNERS and a double-check.
On 2016/10/05 13:55:07, Charlie Harrison wrote: > Thanks, yeah that was my take as well. I was just nervous that there might be > security implications because this is login code. > > +vabr for OWNERS and a double-check. Sorry for the delayed response, I had some unexpected long meetings yesterday. LGTM! The DCHECK is equivalent to the NOTREACHED before, and the lack of handling it will only surface if there is actually a bug. In that case, surfacing that bug is a good thing. Cheers, Vaclav
The CQ bit was checked by csharrison@chromium.org
The CQ bit was unchecked by csharrison@chromium.org
The CQ bit was checked by csharrison@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Simplify origin logic in login_handler This code had logic for continuing execution after a NOTREACHED(), which is against the style guide. With this removed the code is much simpler. ========== to ========== Simplify origin logic in login_handler This code had logic for continuing execution after a NOTREACHED(), which is against the style guide. With this removed the code is much simpler. ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Simplify origin logic in login_handler This code had logic for continuing execution after a NOTREACHED(), which is against the style guide. With this removed the code is much simpler. ========== to ========== Simplify origin logic in login_handler This code had logic for continuing execution after a NOTREACHED(), which is against the style guide. With this removed the code is much simpler. Committed: https://crrev.com/e406acaf0d5e19c1f13161f0e2c7d552329dfebe Cr-Commit-Position: refs/heads/master@{#424840} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/e406acaf0d5e19c1f13161f0e2c7d552329dfebe Cr-Commit-Position: refs/heads/master@{#424840} |