Skip to content

502 bad gateway after reporting a new issue on v34.0.0 #3352

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

Closed
miketaylr opened this issue Jun 16, 2020 · 2 comments
Closed

502 bad gateway after reporting a new issue on v34.0.0 #3352

miketaylr opened this issue Jun 16, 2020 · 2 comments
Assignees

Comments

@miketaylr
Copy link
Member

I've redeployed v33.0.0, so we're good on that front. But we need to figure out what happened.

https://github.com/webcompat/webcompat.com/blob/master/CHANGELOG.md#3400---2020-06-16

@miketaylr
Copy link
Member Author

@ksy36 discovered that any issue that was reported wasn't lost, it went to the right private repo, but the issue route is somehow busted (even for older issues)

@miketaylr
Copy link
Member Author

It seems like it's throwing here:

ERROR in app: Exception on /issues/2497 [GET]#012Traceback (most recent call last):#012 File "./webcompat/templates/__init__.py", line 33, in get_checksum#012

Jun 16 19:27:59 staging-server webcompat-staging: FileNotFoundError: [Errno 2] No such file or directory: '/staging.webcompat.com/webcompat/static/dist/flashed-messages.e5.js'

miketaylr pushed a commit that referenced this issue Jun 16, 2020
Fixes #3352 - correct script location for es5 version of flashed-messages.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants