Skip to content

Contributors #4

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

Merged
merged 5 commits into from
Feb 5, 2023
Merged

Contributors #4

merged 5 commits into from
Feb 5, 2023

Conversation

gkellogg
Copy link
Member

@gkellogg gkellogg commented Feb 3, 2023


💥 Error: 500 Internal Server Error 💥

PR Preview failed to build. (Last tried on Feb 5, 2023, 11:38 PM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.

🔗 Related URL


😭  Sorry, there was an error generating the HTML. Please report this issue!
Specification: http://labs.w3.org/spec-generator/uploads/BtykMO/spec/index.html?isPreview=true%3FisPreview%3Dtrue&publishDate=2023-02-05
ReSpec version: 32.7.0
File a bug: https://github.com/w3c/respec/
Error: Error: Evaluation failed: Timeout: document.respec.ready didn't resolve in 28326ms.
    at ExecutionContext._ExecutionContext_evaluate (/u/spec-generator/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:229:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ExecutionContext.evaluate (/u/spec-generator/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:107:16)
    at async generateHTML (/u/spec-generator/node_modules/respec/tools/respecDocWriter.js:221:12)
    at async toHTML (/u/spec-generator/node_modules/respec/tools/respecDocWriter.js:92:18)
    at async Object.generate [as respec] (file:///u/spec-generator/generators/respec.js:15:44)
    at async file:///u/spec-generator/server.js:252:48

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

@@ -80,7 +80,7 @@
section. Since the edits to this document do not invalidate
previous implementations the Director decided no new implementation report was required. </p>

<section id="related" data-include="./common//related.html"></section>
<section id="related" data-include="./common/related.html"></section>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not work (for me at least) when viewed locally (all specs). I get a reSpec error and a reSpec warning.

Is there some magic I'm missing?

@gkellogg
Copy link
Member Author

gkellogg commented Feb 5, 2023

There’s an outstanding bug in ReSpec (https://github.com/w3c/respec/issues/4378#issuecomment-1416860913) that halts processing in this spec, in particular. I have a workaround that re- defines the “SAX” reference in localBibliogrsph, but wanted to give them a chance to fix it. (If you just remove [[SAX]] in your local copy, it should build).

but, it seems to work in all other RDF specs for me. The problem I mentioned is only on RDF-XML, which has prevented merging this PR. The set of docs seems to show for rdf-concepts. Where are you seeing the problem?

@gkellogg
Copy link
Member Author

gkellogg commented Feb 5, 2023

The data-include stuff might be a problem if you just load the file in a browser window directly. I use python -m http.server and access via localhost.

@afs
Copy link
Contributor

afs commented Feb 5, 2023

Yes, I load the specs as file:///.

I can use Fuseki (!!).

@gkellogg gkellogg merged commit d92b15d into main Feb 5, 2023
@gkellogg gkellogg deleted the contributors branch February 5, 2023 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants