Skip to content
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

Make multipage flag specifically target release and/or nightly #1345

Merged
merged 1 commit into from
Jun 3, 2024

Conversation

tidoust
Copy link
Member

@tidoust tidoust commented Jun 3, 2024

The job still fails to load the ED of the CSS 2.2 spec to extract the list of pages, even with optimized loading (added in last commit). Something's rotten in the State of Network.

In practice, build does not need to load the ED of the CSS 2.2 spec. It just does it because the spec is identified as multipage due to the /TR version. To avoid unnecessary spec loads, this update converts the multipage flag from a boolean to a string with 3 possible values: "all", "release", "nightly". The extraction of the list of pages is now only done on the version targeted by the multipage property.

The update also serializes the extraction of pages to avoid sending too many requests at once. There are only a handful of specs for which we need to look for pages, serialization should not make build much longer than it already is.

The job still fails to load the ED of the CSS 2.2 spec to extract the list of
pages, even with optimized loading (added in last commit). Something's rotten
in the State of Network.

In practice, build does not *need* to load the ED of the CSS 2.2 spec. It just
does it because the spec is identified as multipage due to the /TR version. To
avoid unnecessary spec loads, this update converts the `multipage` flag from a
boolean to a string with 3 possible values: "all", "release", "nightly". The
extraction of the list of pages is now only done on the version targeted by the
`multipage` property.

The update also serializes the extraction of pages to avoid sending too many
requests at once. There are only a handful of specs for which we need to look
for pages, serialization should not make build much longer than it already is.
Copy link
Member

@dontcallmedom dontcallmedom left a comment

Choose a reason for hiding this comment

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

note that at least one of the recent failures was for the SVG2 spec rather than CSS2

@tidoust tidoust merged commit 88c0fad into main Jun 3, 2024
1 check passed
@tidoust tidoust deleted the multipage branch June 3, 2024 14:16
@tidoust
Copy link
Member Author

tidoust commented Jun 3, 2024

note that at least one of the recent failures was for the SVG2 spec rather than CSS2

Yes, and the situation is worse in Webref, we just don't see it ;)
I created w3c/webref#1244 to explore and track the issue.

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