-
Notifications
You must be signed in to change notification settings - Fork 22
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
Fail to generate respec files with non-HTML data-include #140
Comments
It successfully loaded But I can see the files from |
(I'll leave it to @gkellogg to reply - thanks a lot for already looking into this!) |
Thanks @dontcallmedom. I perhaps should have just created the issue, but I thought there may have been some requirement I was unaware of. The error comes up in the "Generate Static HTML" step that it can't fetch
And, as I said in the email, running this locally on my Mac does not show the same error.
The GH Action seems to be running exactly the same version of ReSpec. |
The "failed to fetch" part is just a warning, you can ignore it. spec-prod (not ReSpec) tries to recursively find all referenced resources (HTML files, markdown, images etc.) from the built spec (i.e. after ReSpec builds it) to copy them to a to-be-deployed directory. This warning exists as spec-prod assumed the ebnf file to be HTML and tried to fetch its linked subresources (it failed here). But it still successfully copied the ebnf file. Looking further at the CI log, it seems your build failed at the link checker step. If rightly so, I would encourage you to disable link checking entirely as it's very experimental and I haven't had the time/motivation to fix it yet. |
Thanks @sidvishnoi. It would be great if it were easier to find the specific causes of errors in the GH Action output; I had missed the link-checker error, but it did find some dead URLs. It seems that this issue really belonged against w3c/spec-prod after all. |
#133 will be helpful there. |
reported by @gkellogg in https://lists.w3.org/Archives/Public/spec-prod/2022AprJun/0022.html
The text was updated successfully, but these errors were encountered: