-
Notifications
You must be signed in to change notification settings - Fork 101
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
Nokogiri::CSS::SyntaxError: unexpected '|' after '#<Nokogiri::CSS::Node:0x000000012ae10458>' #120
Comments
Same Problem here (odf-report 0.7.2), results in same stack trace. 1.13.0 works fine, 1.13.1 fails with this. |
@sandrods This is preventing me from upgrading Nokogiri to patch a CVE GHSA-fq42-c5rg-92c2 |
Sorry, folks. Gonna take a look at it ASAP
…On Tue, 22 Feb 2022 at 19:32 Shane Cavanaugh ***@***.***> wrote:
@sandrods <https://github.com/sandrods> This is preventing me from
upgrading Nokogiri to patch a CVE GHSA-fq42-c5rg-92c2
<https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-fq42-c5rg-92c2>
—
Reply to this email directly, view it on GitHub
<#120 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAABUWJ6RCQXAILNYOKDT5LU4QFIPANCNFSM5OMZDHJQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Well, pipes are part of CSS3 specifications, and are used to query using namespaces https://www.w3.org/TR/selectors-3/#univnmsp I'll have to look into it further. It may be a regression bug in Nokogiri, since it worked until 1.13.0. I may need to translate these queries into xpath. Right now I have no clue. Will keep you all posted. Any directions would be appreciated |
… with new version of Nokogiri. See #120
I think I might have fixed it. My specs are green now. |
It's working for me. Thanks! |
closed by 1fb39e1 |
Works like a charm for me. Thank you so much! |
According to the sandrods#120, it seems it happened at v1.13.1.
This is an issue that exists with Nokogiri 1.13.1, but not 1.13.0. There was a change in how XPath selectors are handled in CSS rules1 but I don't know enough to be certain that's the cause.
Failure here:
odf-report/lib/odf-report/table.rb
Line 75 in 16f5b38
Backtrace:
Footnotes
https://github.com/sparklemotion/nokogiri/issues/2419 ↩
The text was updated successfully, but these errors were encountered: