Same commit deployment is now broken

[p.aarseth]

Hi,

It looks like there’s something wrong with the build & deployment system. I have a commit that was deployed April 5th that is working as expected. Yesterday and today everything I deploy is broken.

Multiple pages take 10-20 seconds to redirect to and when I get there there’s no content.
There’s also a new console.error complaining about redeclaring a constant.

When I tried to re build and deploy the same working commit from April 5th, it’s also broken.

buildID of the original one that works April 5th: 624ca8971ca49e00088ea4ab
buildID of the same commit today April 7th that is broken (deployed with purged cache): 624eeba6089a7500b5eee57b

May or may not be related to

Frontend freezing, not loading, waiting for cache

We’re having multiple problems with whyfry-app. Sometimes the website doesn’t launch and gets stuck at “waiting for cache”. Sometimes the web app freezes mid usage with no errors. Sometimes the app doesn’t start a connection to our api, making it stuck on the loading screen. This happens like 10% of the time. We only get a error after 10 minutes of waiting, while the screen is stuck. We’ve ran our frontend locally, connected to our production backend. We can’t replicate the problems. This hap…

[solvengo]

Does your “site is live” message in build log also appear too early?

[p.aarseth]

No, it’s the second to last line like normal.

[p.aarseth]

Turns out this came from one of my dependencies suddenly being MIA, which meant that all new builds would come out broken.

[hillary]

Thanks for coming back and sharing your solution, @p.aarseth. Glad everything is working now! If you have further questions / if this comes up again, don’t hesitate to reach out.

Happy building