You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
regex crate just recieved a 1.9.0 update, however, all test cases under regex.rs does not produce output for some reason.
I tried running TESTNAME='regex' cargo uitest on stable branch, and it fails on either windows or linux platform.
Then I manually modify Cargo.lock and set the version of regex to 1.8.4, and regex-syntax to 0.7.2, and everything works normal.
Which is kinda weird, can someone confirm this please? Should Cargo.lock be included in the future?
Version
No response
Additional Labels
No response
The text was updated successfully, but these errors were encountered:
yep, apparently the path to Regex changed and that broke the lint. It was causing CI to fail for all PRs too, however #11111 just got merged and that should have fixed this. Are you on the latest commit? (edit: oh I missed that you said "stable")
yep, apparently the path to Regex changed and that broke the lint. It was causing CI to fail for all PRs too, however #11111 just got merged and that should have fixed this. Are you on the latest commit? (edit: oh I missed that you said "stable")
ahhh~ glad to know it has already been fixed, but I guess I have to manually set regex version each time until that commit made it to the next stable 🤦♂️, thank you though, closing this right now.
Description
regex
crate just recieved a1.9.0
update, however, all test cases under regex.rs does not produce output for some reason.I tried running
TESTNAME='regex' cargo uitest
on stable branch, and it fails on either windows or linux platform.Then I manually modify Cargo.lock and set the version of
regex
to 1.8.4, andregex-syntax
to 0.7.2, and everything works normal.Which is kinda weird, can someone confirm this please? Should
Cargo.lock
be included in the future?Version
No response
Additional Labels
No response
The text was updated successfully, but these errors were encountered: