Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No more data from omahaproxy #3

Open
janbrasna opened this issue Apr 7, 2024 · 3 comments
Open

No more data from omahaproxy #3

janbrasna opened this issue Apr 7, 2024 · 3 comments

Comments

@janbrasna
Copy link

https://omahaproxy.appspot.com/

*** Service Permanently Offline ***

OmahaProxy has been turned down.
Please migrate to https://chromiumdash.appspot.com.

Announcement: https://groups.google.com/a/chromium.org/g/chromium-dev/c/uH-nFrOLWtE/m/PhUj_inyAQAJ

I'm looking into https://developer.chrome.com/blog/chrome-for-testing/ data and JSON endpoints for mapping milestone versions to revisions — and once you have a revision you can link to the chromium snapshots archive with it (instead of the chrome-testing endpoints it was designed for) so there might be viable alternatives.

@vikyd
Copy link
Owner

vikyd commented Apr 8, 2024

Good idea, will be fixed in the next few days.

@janbrasna
Copy link
Author

Looking into it further, there a) seems to be an endpoint providing the data live https://chromiumdash.appspot.com/fetch_version?version=110.0.5481.61 (not sure how happy they'd be to have it called from outside or crawled thou;D) or b) there's a gh-pages "cached" built output of the mapping for chrome-for-testing json calls (can't tell if that one has saved all the versions or just known good, and a as a note contains only data starting w/ CfT so 112+…)

@MikeMcC399
Copy link

@vikyd

Good idea, will be fixed in the next few days.

Are you still intending to fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants