-
Notifications
You must be signed in to change notification settings - Fork 182
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for NFKD and the decomposed counterpart of UTS 46 without…
… ignored and disallowed (#1967)
- Loading branch information
Showing
32 changed files
with
34,956 additions
and
2,697 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
a3ba544
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
1
.provider/testdata/data/testdata.postcard
2301197
bytes2221790
bytes1.04
This comment was automatically generated by workflow using github-action-benchmark.
CC: @gnrunge @sffc @zbraniecki @echeran
a3ba544
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The increase in data is expected because this PR adds normalization-related data to testdata. This occurred in the
datasize
CI job.Another non-issue (as Henri predicted) is that one of the CI runs during development the PR had a failure due to flakiness. That occurred in the
binsize
CI job, and was due to Github Actions infrastructure internal issues. That job passed on the CI run triggered by the merge tomain
.