Correct requirement of well-formed code-unit sequence #951
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
|
@pradyunsg Could you please elevate this PR? This was a serious mistake, and it needs our attention. |
ChristianSi
suggested changes
Jan 13, 2023
|
Oops? 😅 Thanks for catching this @ChristianSi and for the quick PR on this @eksortso. Much appreciated! |
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.
As pointed out by @ChristianSi in #929, a last-minute change to the text for the "well-formed code-unit sequence" requirement inadvertantly invalidates all TOML files.
This PR corrects that text.
I ask that, at minimum, both @ChristianSi and @pradyunsg review this correction.