Release v0.7.6
This release fixes another panic-related problem discovered by @aclemmensen (thanks!), and makes miscellaneous other fixes, generally in an attempt to get to them before Asbjørn does.
mischov
mischov
No release this time, though once Rustler releases with a fix for a compilation problem related to ERTS 9.2, I’ll be releasing as well.
Instead, I’d like to get feedback and suggestions for an issue that recently came to my attention regarding to how much memory Meeseeks uses when parsing large HTML files (spoiler, it’s a lot).
2
mischov
OvermindDL1
brightball
mischov
While I think it would be correct to say that the underlying parsers (html5ever and xml5ever) are streaming parsers, Meeseeks does not support using them in any streaming fashion (Meeseeks expects a document to query).
2
OvermindDL1
mischov
Not really, the document is build in the Rust portion of meeseeks_html5ever.
If you wanted a stream of events you’d need to create some kind of consumer (in Rust) for the html/xml5ever parsers that somehow streamed the events into Elixir?
1
brightball
Just wondering. With XML at least, DOM parsing makes it easier to hop around a document and get various pieces of data, but SAX parsers are tremendously more efficient if you’re scripting a large volume.
I haven’t used meeseeks yet to know if it was an option but just figured I’d toss it out there because of the memory issue on large documents mentioned above.
HTML parsers tend to have to correct a lot of malformed HTML so I didn’t know if SAX was viable there.
2
mischov
Release v0.8.0
This release:
- Ensures Elixir 1.6 compatibility
- Adds a
.formatters.exsand formats the project - Fixes some typespec errors, thanks to @OvermindDL1 for raising the issue
- Adds
Document.delete_node/2, thanks to @willbarrett for the contribution - Adds
get_root_ids/1,get_node_ids/1, andfetch_node/2toDocument - Improves the safety of many
Documentfunctions by raising whennode_iddoes not exist in the Document (before they might have raised or might have handled the problem gracefully)
Special thanks to Will, who becomes the first code contributor other than myself.
4