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
When processing a file that has a long line (no line breaks), the plugin takes more time than expected. This becomes especially problematic when content is markdown that includes an embedded image whose long base64 encoding is on a single line. Here is a small example using ipsum lorem: https://gist.github.com/sfc-gh-pmardziel/15c1242a9e4e3760ba15a0d324d414da . This example takes about 50 seconds to process the computation that is indicated by this --verbose logline:
DEBUG - Running `page_markdown` event from plugin 'include-markdown'
Note that in this example and in base64 encodings, the default opening_tag and closing_tag are not found anywhere in the line and changing them to something that is longer/harder to match has no affect on the slowness. I thus theorize that some other aspect of the regex that is being matched is responsible for the long run time.
As a workaround, with v6.2.0 you can include the image in your markdown file using recursive=false and the regex will not be applied to that long line.
When processing a file that has a long line (no line breaks), the plugin takes more time than expected. This becomes especially problematic when content is markdown that includes an embedded image whose long base64 encoding is on a single line. Here is a small example using ipsum lorem: https://gist.github.com/sfc-gh-pmardziel/15c1242a9e4e3760ba15a0d324d414da . This example takes about 50 seconds to process the computation that is indicated by this
--verbose
logline:Note that in this example and in base64 encodings, the default
opening_tag
andclosing_tag
are not found anywhere in the line and changing them to something that is longer/harder to match has no affect on the slowness. I thus theorize that some other aspect of the regex that is being matched is responsible for the long run time.Environment:
This is an "Apple M1" mac in case it wasn't clear from that uname.
The text was updated successfully, but these errors were encountered: