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

Web/HTML/Using_the_application_cache stopped working since whoami changed #4011

Closed
peterbe opened this issue Jun 11, 2021 · 5 comments
Closed

Comments

@peterbe
Copy link
Contributor

peterbe commented Jun 11, 2021

@peterbe I don't think this site works https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache.

Still down for me. And chrome console shows the same error as before.

react-dom.production.min.js:216 TypeError: Cannot read property 'flags' of undefined
    at Q (index.tsx:69)
    at al (react-dom.production.min.js:157)
    at Vl (react-dom.production.min.js:180)
    at Hi (react-dom.production.min.js:269)
    at _u (react-dom.production.min.js:250)
    at Ou (react-dom.production.min.js:250)
    at xu (react-dom.production.min.js:250)
    at yu (react-dom.production.min.js:243)
    at react-dom.production.min.js:123
    at t.unstable_runWithPriority (scheduler.production.min.js:18)

Originally posted by @ZeddYu in #4010 (comment)

@peterbe
Copy link
Contributor Author

peterbe commented Jun 11, 2021

The problem with https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache is that it should have been pruned long ago. It's a stale page that's stuck in S3. It's not part of archived content.
We're currently not pruning the existing built and published pages because we're still waiting to delete all the archived content URLs (June 30, 2021).

So once that goes into effect, this page will become 404 instead of a 200 with a broken JS.

CC @escattone @ZeddYu

@peterbe
Copy link
Contributor Author

peterbe commented Jul 14, 2021

@escattone This is another page/issue that should automatically resolve once we turn the pruning back on. Let's remember to check.

@peterbe
Copy link
Contributor Author

peterbe commented Jul 21, 2021

Got fixed when we enabled pruning again after deleting the archived content.

@peterbe peterbe closed this as completed Jul 21, 2021
@ZeddYu
Copy link

ZeddYu commented Jul 22, 2021

@peterbe It seems the issue has been fixed. But Is there any other way to read this document online now?

@peterbe
Copy link
Contributor Author

peterbe commented Jul 22, 2021

@peterbe It seems the issue has been fixed. But Is there any other way to read this document online now?

I filed mdn/content#7158

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