Repository navigation
Conversation
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
1 participant
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 today input was checked only for its character pattern. Impossible dates such as February 30 and out-of-range timezone offsets passed the check, so the action could run judges and spend API quota before XSLT rejected the value.
The entry script now validates the calendar and time with Ruby's ISO-8601 parser and enforces the XML Schema timezone limit of -14:00 through +14:00 before updating the factbase.
Checks: Bash syntax validation and entry-script scenarios for an impossible calendar date and timezone offsets beyond the supported range.
Closes #920