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

The observatory rating is not updating #128

Open
TruncatedDinoSour opened this issue Feb 11, 2025 · 3 comments
Open

The observatory rating is not updating #128

TruncatedDinoSour opened this issue Feb 11, 2025 · 3 comments

Comments

@TruncatedDinoSour
Copy link

I've added https://pb.ari.lt/ to https://privatebin.info/directory/ a few days ago yet it still shows that the rating is "Unrated" whereas it has a rating of A+ (https://developer.mozilla.org/en-US/observatory/analyze?host=pb.ari.lt). I find it weird and I saw an issue about this made in 2023 at #47 but I think it has broke again. Did the update time change? Any extra process? I'm confused :)

Making a new issue because #47 been closed for a while n.

@elrido
Copy link
Contributor

elrido commented Feb 11, 2025

I can see the same behaviour: The result we get on the new API and the one displayed on the website are often out of sync. I've not investigated further because in the cron logs I do see new instances eventually getting updated, but it can take up to a week, then there are usually 2-3 updated at the same time. I wonder if our service gets rate limited (it will request several hundred such results from the API in parallel) or this is due to some CDN caching on Mozillas side.

If anyone has suggestions how to debug this further let me know - I can execute scripts or such from the VM in question, so same request-IP as the service.

@TruncatedDinoSour
Copy link
Author

It took 2 weeks for it to get updated... but now it's there? Cool, I guess. But I don't think it should take 2 weeks so I think it's valid to keep this open?

@elrido
Copy link
Contributor

elrido commented Feb 27, 2025

I see no reason to close this and I do not know how to resolve it. This started occurring when the API got changed and the new API does not report any errors correctly. The requests either seem to work and simply don't report any updates or time out - as stated, I have no ideas how we can diagnose these any further from our end. Has anyone reported this at Mozilla? Any ideas what I can do to resolve 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

2 participants