-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Error after upgrading to 0.35.0 #492
Comments
I'm into it. @aselder Is it possible to provide a snippet so I can reproduce the error? |
I’m working on digging into exactly which snippet triggered the error. Hopefully I have it narrowed down by tomorrow ThanksAndrewSent from my iPhoneOn Oct 16, 2023, at 1:13 PM, Philip Sampaio ***@***.***> wrote
I'm into it. @aselder Is it possible to provide a snippet so I can reproduce the error?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
OK, thank you! |
Here’s some info that I think clarifies the root cause. I just tried to parse that html that was found to be bad on the one page:
With Floki 0.35.0, I get the same exact error we saw on production:
with Floki 0.34.3, it works:
So it was some invalid html that was not causing problem before, but after upgrading floki, it was an error |
@aselder thank you so much! It was a silly mistake of mine. I'm going to release a patch version soon :) |
Done! Please try the version |
Description
[error] GET /products/scalp-solutions-dry-scalp-treatment ** (MatchError) no match of right hand side value: [{"=", "="}, {""trade"", ""trade""}]
(floki 0.35.0) src/floki_mochi_html.erl:257: :floki_mochi_html.norm/2
(floki 0.35.0) src/floki_mochi_html.erl:241: :floki_mochi_html.tree/3
(floki 0.35.0) src/floki_mochi_html.erl:120: :floki_mochi_html.parse_tokens/2
(floki 0.35.0) lib/floki/html_parser/mochiweb.ex:10: Floki.HTMLParser.Mochiweb.parse_document/2
(tenant_web 0.1.0) lib/tenant_web/components/blocks/text.ex:130: TenantWeb.Components.Blocks.Text.maybe_render_with_existing_container/1
(tenant_web 0.1.0) lib/tenant_web/components/blocks/text.ex:17: TenantWeb.Components.Blocks.Text.render/1
(phoenix_live_view 0.19.5) lib/phoenix_live_view/tag_engine.ex:68: Phoenix.LiveView.TagEngine.component/3
To Reproduce
Steps to reproduce the behavior:
# An example to reproduce the problem
Expected behavior
A description of what is the expected behavior using the code.
The text was updated successfully, but these errors were encountered: