https://blue-build.org/ logo
Build Errors
# questions
j
Not sure what happened, but my Github action started failing today. Seems to happen after fetching the JSON schemas.
Copy code
[17:31:37 DEBUG] => Logged into ghcr.io
logged in via /home/runner/.docker/config.json
[17:31:37 DEBUG] => Logged into ghcr.io
[17:31:37 DEBUG] => Retrieving schema from https://schema.blue-build.org/stage-v1.json
[17:31:37 DEBUG] => Retrieving schema from https://schema.blue-build.org/import-v1.json
[17:31:37 DEBUG] => Retrieving schema from https://schema.blue-build.org/module-v1.json
[17:31:37 DEBUG] => Retrieving schema from https://schema.blue-build.org/module-custom-v1.json
[17:31:37 ERROR] => Failed:
  × [] has less than 1 item
https://github.com/jonerrr/os-image
a
message has been deleted
c
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.
g
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
j
could it have something to do with the fact that my modules folder is empty (e.g. only a
.gitkeep
)?
g
No, this is happening to me as well
j
hmm weird
g
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 empty
j
ohhh
g
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 that
and i'm not seeing any issues
in the logs
g
That module.json file is not supposed to be empty though
here it is
g
Fun rate limiting
x
i think the github action is rate-limited from quering github too much 😭
g
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
x
i'm working on giving it a token that shouldn't get rate-limited
g
Looks like re-deploying the site did the trick for now
I can run builds again
x
good good
j
yup looks like its fixed
ty!