Regex parse error at tracing-subscriber-0.3.16\src\filter\env\directive.rs:140:10

[dbidwell94]

Bug Report

Version

0.3.16

Platform

Windows 11 64bit

Crates

sea-orm-cli

Description

Crate fails to build due to the following error:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Syntax(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
regex parse error:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 1: (?x)
 2:             ^(?P<global_level>(?i:trace|debug|info|warn|error|off|[0-5]))$ |
                                      ^
 3:                 #                 ^^^.
 4:                 #                     `note: we match log level names case-insensitively
 5:             ^
 6:             (?: # target name or span name
 7:                 (?P<target>[\w:-]+)|(?P<span>\[[^\]]*\])
 8:             ){1,2}
 9:             (?: # level or nothing
10:                 =(?P<level>(?i:trace|debug|info|warn|error|off|[0-5]))?
11:                     #          ^^^.
12:                     #              `note: we match log level names case-insensitively
13:             )?
14:             $
15:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: Unicode-aware case insensitivity matching is not available (make sure the unicode-case feature is enabled)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
)', C:\Users\dbidw\.cargo\registry\src\g.yxqyang.asia-1ecc6299db9ec823\tracing-subscriber-0.3.16\src\filter\env\directive.rs:140:10

[billy1624]

Seems like manually enable the unicode-case feature in regex inside the application Cargo.toml would work.

regex = { version = "1", features = ["unicode-case"] }

However, I think tracing-subscriber should enable the unicode-case feature in regex by default.

[dbidwell94]

You beat me to it!

[billy1624]

Detailed Discord chat log: https://discord.com/channels/873880840487206962/1098838564290187324

[dbidwell94]

I have submitted a PR for approval which should fix this issue.

[BurntSushi]

I posted an analysis of what I believe is happening here: rust-lang/regex#982 (comment)

[dbidwell94]

I posted an analysis of what I believe is happening here: rust-lang/regex#982 (comment)

I have taken your feedback and refactored the regex in the PR instead of adding the features. Thanks!