refactor respec config to avoid race condition#477
Merged
Conversation
himorin
approved these changes
Feb 3, 2026
Contributor
|
approve, but I don't think we'll not rely on spec-generator (or echidna) but use manual publication (due to various issues, including timeout from long processing time) only once as final update, when @kidayasuo concludes discussion around #453 . |
Member
Author
|
The fixes in that PR also apply for regular use of respec. I'm mentioning spec-generator because that's where @xfq filled out the issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
deferattribute on the respec script can cause some race condition with spec-generator.That PR removes the attribute and fixes the group associated with the document.
Fix w3c/spec-generator#396
/cc @kfranqueiro