Build Errors
Not sure what happened, but my Github action started failing today. Seems to happen after fetching the JSON schemas.
https://github.com/jonerrr/os-image
GitHub
GitHub - jonerrr/os-image: This is my personal OS image.
This is my personal OS image. Contribute to jonerrr/os-image development by creating an account on GitHub.
20 Replies
I have the same issue and have reported it on the cli repository. I have found that if I turn on —skip-validation things still build.
I'll check on that in a moment, seems weird.
Ok, after adding some extra errors, I narrowed the problem down to the https://schema.blue-build.org/module-v1.json schema file
could it have something to do with the fact that my modules folder is empty (e.g. only a
.gitkeep)?No, this is happening to me as well
hmm weird
If you look at that link, the
anyOf in there is supposed to have a bunch of refs to the module schema files
It's emptyohhh
Yeah something screwed up with our schema builder
@xyny could you check on the cloudflare builder just in case?
Looks like the https://blue-build.org/modules.json is empty
The
fetchModules.js script pulls thatit's on github nowadays https://github.com/blue-build/website/actions/runs/18261157763/job/51989253518
GitHub
Deploy · blue-build/website@75f1ce2
Website that hosts BlueBuild documentation. Contribute to blue-build/website development by creating an account on GitHub.
and i'm not seeing any issues
in the logs
That module.json file is not supposed to be empty though
GitHub
Deploy · blue-build/website@75f1ce2
Website that hosts BlueBuild documentation. Contribute to blue-build/website development by creating an account on GitHub.
here it is
Fun rate limiting
i think the github action is rate-limited from quering github too much 😭
Would you be able to make it fail if it ran into that situation?
That way we don't end up with broken schemas
I'm running the deploy again so that we can get back up and running
i'm working on giving it a token that shouldn't get rate-limited
Looks like re-deploying the site did the trick for now
I can run builds again
good good
yup looks like its fixed
ty!