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

Website results in 404 error #6255

Closed
noahtallen opened this issue May 24, 2018 · 21 comments
Closed

Website results in 404 error #6255

noahtallen opened this issue May 24, 2018 · 21 comments
Labels

Comments

@noahtallen
Copy link

Accessing the website results in 404 error. (same issue as yesterday)

@lirbank
Copy link
Contributor

lirbank commented May 24, 2018

Going directly to the docs works though, just the landing page seems to be gone.

This works -> https://facebook.github.io/jest/docs/en/api.html

@thymikee
Copy link
Collaborator

cc @ericnakagawa – we're experiencing some flakiness in website deploy, could you have a look a it?

@captbaritone
Copy link
Contributor

Seems to be back up for me.

@SimenB
Copy link
Member

SimenB commented May 25, 2018

Yeah, it went back up by the time @thymikee commented. Not really sure what's going on, or if it's the "fault" of docusaurus, circle ci or github pages

@chinesedfan
Copy link
Contributor

It works now.

@SimenB
Copy link
Member

SimenB commented Jun 1, 2018

Not sure what's going on - it seems like the redirect from https://facebook.github.io/jest/ to https://facebook.github.io/jest/en (notice language at the end) is down during deploys. I suspect either crowdin or docosaurus is doing something weird.

@ericnakagawa @JoelMarcey ideas?

@JoelMarcey
Copy link
Contributor

@SimenB Can you provide a bit more context? The site seems functional now. Am I missing something there?

What exactly was done when you noticed that the site was down to make it come back up?

Just trying to figure out if there is something reproducible here.

@SimenB
Copy link
Member

SimenB commented Jun 1, 2018

It's during deploy. You might be able to reproduce by triggering a deploy of the website?

@JoelMarcey
Copy link
Contributor

Right. I understand that I think. But now the site is functional (right?). What was done to make the site functional again? Or are you saying that once the deploy is finished, the site is fine. i.e., in the seconds/minutes that the site is deploying, you get the funky behavior, but after that, all is good?

@SimenB
Copy link
Member

SimenB commented Jun 1, 2018

Yes, correct. I wonder if it's related to crowdin, as it takes a few minutes and the thing that's gone is the default language redirect

@JoelMarcey
Copy link
Contributor

Talking to some folks here, @ericnakagawa and @rickyvetter

Perhaps something happening when pages are being built and pages get deleted before completing. The issue reported mentioned pages "showing up" later. That sounds like something is delayed maybe something with their Github's gh-pages deployment.

almost certainly not a crowdin issue because all of the crowdin interaction happens before you git push. its either an issue with gh-pages deployment or with the browser cache.

@SimenB
Copy link
Member

SimenB commented Jun 20, 2018

#6508 :(

@JoelMarcey
Copy link
Contributor

@SimenB that issue you referenced is closed now. Is there still a problem?

Also, what version of Docusaurus are you running now? 1.2.1? That’s the latest.

Sent with GitHawk

@SimenB
Copy link
Member

SimenB commented Jun 20, 2018

Yeah, it fixes itself. But it still happens. We're in 1.0.14. Should we upgrade?

@JoelMarcey
Copy link
Contributor

There have been a bunch of fixes since then. It may help. You can look at the Changelog see what has been added and fixed.

Of course, run locally first to make sure nothing breaks.

cc @yangshun @endiliey

Sent with GitHawk

@yangshun
Copy link
Contributor

yangshun commented Jun 20, 2018

@SimenB Do we know why it fixes itself?

Yeah, it fixes itself. But it still happens. We're in 1.0.14. Should we upgrade?

Yes, please! Actually, we'll release 1.3.0 soon and I can help to do an upgrade for Jest.

@SimenB
Copy link
Member

SimenB commented Jun 21, 2018

Do we know why it fixes itself?

No, but I suspect (without evidence) that it's down during deploy, but comes up again after deploy is done. There was a merge-spree for PRs yesterday, same as the last time (this issue was opened when we merged PRs for the Jest 23 release).

Actually, we'll release 1.3.0 soon and I can help to do an upgrade for Jest.

Great, I'll hold off then 🙂

@endiliey
Copy link
Contributor

1.3.0 is released 😊

@yangshun
Copy link
Contributor

I updated Docusaurus to 1.3.0 here but CI seems to fail because of Prettier. I'm not sure if I fixed it correctly because I don't see any autofix command for scripts in package.json.

@SimenB
Copy link
Member

SimenB commented Jul 6, 2018

Hopefully fixed

@SimenB SimenB closed this as completed Jul 6, 2018
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

9 participants