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

Issue 881255 link

Starred by 2 users

Issue metadata

Status: Closed
Owner:
Closed: Sep 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Error 404 is displaying when requesting a view change log(for recent ranges) on OmahaProxy

Project Member Reported by rbasuvula@chromium.org, Sep 6

Issue description

Chrome Version: #71.0.3544.0
OS: All.

Steps to reproduce the problem:
1. Open https://omahaproxy.appspot.com.
2. Under "Change log", enter two Chrome versions (for example, 71.0.3543.0 and 71.0.3544.0).
URL: https://chromium.googlesource.com/chromium/src/+log/71.0.3543.0..71.0.3544.0?pretty=fuller&n=10000
3. Check "View Change Log".
4. Click on it.

What is the expected behavior?
Change log should be shown properly with available change logs.

What went wrong?
Error 404 page is displaying.

Note:
1. Its working fine in previous versions #71.0.3542.0 and 71.0.3543.0.
URL : https://chromium.googlesource.com/chromium/src/+log/71.0.3542.0..71.0.3543.0?pretty=fuller&n=10000
2. 71.0.3544.0 available to users ~2 hrs ago, and crash data is available.
 
Cc: gov...@chromium.org abdulsyed@chromium.org ligim...@chromium.org mmoss@chromium.org
Owner: waff...@chromium.org
Status: Assigned (was: Untriaged)
Cc: rsesek@chromium.org
Status: Closed (was: Assigned)
The log is available now; I guess it takes time for a new version to appear.
Those logs are an inherent part of the git information in the repo, so there shouldn't be any issue with delays. If the release has been created, then the version number (release tag) exists in the repo, and the log can be displayed. The only way I know to generate a 404 is if you put in invalid version numbers, like:

https://chromium.googlesource.com/chromium/src/+log/4000.0.0.0..5000.0.0.0?pretty=fuller&n=10000

Could this have just been a typo?
W.r.to Comment #2 & 3, i have observed from last 4 days its working fine for new versions. I have given the correct URL only due to some problem getting 404 error on that day. We will keep on observing the builds and update is there any wired behaviour.

Thank You!


Sign in to add a comment