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 WER file field names with non-ascii characters usable #938

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

pyrco
Copy link
Contributor

@pyrco pyrco commented Nov 7, 2024

We use WER field names as the field names for the records the WER plugin creates. This means they have certain limitations in what characters can be used. Previously all characters in the set [a-zA-Z_] were removed. This patch encodes them as _<utf-8_sequence_in_hex>.

@pyrco
Copy link
Contributor Author

pyrco commented Nov 7, 2024

This improves on #544

It also makes #270 redundant as it accomplishes the same thing in a slightly different way.

When this ticket is merged the issue #790 can be closed.

@pyrco pyrco linked an issue Nov 7, 2024 that may be closed by this pull request
Copy link

codecov bot commented Nov 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.04%. Comparing base (015c33f) to head (01bda18).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #938      +/-   ##
==========================================
+ Coverage   76.98%   77.04%   +0.05%     
==========================================
  Files         322      322              
  Lines       27583    27598      +15     
==========================================
+ Hits        21236    21262      +26     
+ Misses       6347     6336      -11     
Flag Coverage Δ
unittests 77.04% <100.00%> (+0.05%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pyrco pyrco force-pushed the more-robust-wer-field-names branch 2 times, most recently from 671eb8c to e575221 Compare November 8, 2024 08:00
@pyrco
Copy link
Contributor Author

pyrco commented Nov 8, 2024

This PR uncovered a bug in flow.record's field name validation which is fixed in fox-it/flow.record#151

We use WER field names as the field names for the records the WER
plugin creates. This means they have certain limitations in what
characters can be used. Previously all characters in the set [a-zA-Z_]
were removed. This patch encodes them as _<utf-8_sequence_in_hex>.
@pyrco pyrco force-pushed the more-robust-wer-field-names branch from e575221 to 01bda18 Compare November 11, 2024 12:19
@pyrco pyrco merged commit 6a3a745 into main Nov 11, 2024
18 of 20 checks passed
@pyrco pyrco deleted the more-robust-wer-field-names branch November 11, 2024 13:21
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.

Add handling for non-ascii characters PR#270
2 participants