Fix Asciidoc error in vec table #570
Merged
Conversation
This file contains 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
It appears that this error was introduced a while ago in KhronosGroup#480, but it was only flagged recently as an error in the build. The docker image we use to build the spec was updated earlier today, and the new image flags this as an error. It appears that older docker images did not flag an error, but the build output was corrupt. Luckily, we did not publish any of the corrupted builds.
|
Merging as editorial |
keryell
pushed a commit
that referenced
this pull request
Sep 10, 2024
Fix Asciidoc error in vec table
gmlueck
added a commit
that referenced
this pull request
Nov 7, 2024
Fix Asciidoc error in vec table (cherry picked from commit 19c0318)
gmlueck
added a commit
that referenced
this pull request
Nov 7, 2024
Fix Asciidoc error in vec table (cherry picked from commit 19c0318)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It appears that this error was introduced a while ago in #480, but it was only flagged recently as an error in the build. The docker image we use to build the spec was updated earlier today, and the new image flags this as an error. It appears that older docker images did not flag an error, but the build output was corrupt. Luckily, we did not publish any of the corrupted builds.