Open kimadactyl opened 2 weeks ago
@katjam - link in issue ticket suggests a solution but it's out of my depth
Thanks. I did used to use that Netlify cache thing to solve the problem there, but it did stop working a couple times / changed server spec.
For this I am wondering if we pull back to building twice a day. At the moment it's every 3 hours which shouldn't be overlapping - but maybe it overlaps with someone else on same machine? I have no idea how cloudflare allocates these build servers but the problem does seem a lot more frequent than it was on netlify.
I think it's just that there's 3 projects in elm-stuff
that are clashing, no? thats what the link seemed to suggest to me, anyway, that they are all fighting each other
I think it's just that there's 3 projects in
elm-stuff
that are clashing, no? that's what the link seemed to suggest to me, anyway, that they are all fighting each other
Ah yes, I see. It's because :
The elm-pages build command is running two parallel compilation tasks for the client and worker apps creating a race condition.
Dillon says it's been fixed but not sure if that means in v2 or v3. We also need to cut back on event window because there was a recent timeout fail on the whole build.
Looks like that update happened in v3.0 - so for now I'll fix the event window import #391 and we should do an experiment with upgrading to v3.0 when we integrate Manchester because it seems like it'll address a couple things for us.
Description
Site is failing about half the time due to an Elm compilation error. This is significantly reducing our quality of life as our notifications are throwing a lot of false positives, and information updates are inconsistent.
Currently it is as below, but I think the package name has shifted a few times.
Some idea of what might be causing it and a suggested fix is here: https://discourse.elm-lang.org/t/problem-building-dependencies-error-in-pipeline-solved/8755
Steps to reproduce
View Cloudflare build logs on fail