Issue #1 resolved

Runtime error at startup

Anonymous created an issue

Perhaps my ignorance of Erlang, but is this an obvious error (before I go digging into it)?

Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:24:24] [async-threads:0] [hipe] [kernel-poll:false]

Starting... Eshell V5.9.1 (abort with ^G) 1> {"init terminating in do_boot",{badarg,[{re,run,["a href=\"\"","[a-zA-Z0-9!#$%&'+/=?^_{|}~-]+(?:.[a-za-Z0-9!#$%&'*+/=?^_{|}~-]+)@(?:a-zA-Z0-9?.)+(?:[a-zA-Z]{2}|com|org|net|gov|mil|biz|info|mobi|name|aero|jobs|museum)"],[]},{markdown,get_email_addie,1,[{file,"src/markdown.erl"},{line,1031}]},{markdown,openingdiv,1,[{file,"src/markdown.erl"},{line,971}]},{markdown,l1,3,[{file,"src/markdown.erl"},{line,918}]},{markdown,lex,1,[{file,"src/markdown.erl"},{line,903}]},{markdown,conv,1,[{file,"src/markdown.erl"},{line,46}]},{blog,markdown,2,[{file,"src/blog.erl"},{line,123}]},{blog,parse,1,[{file,"src/blog.erl"},{line,117}]}]}}

Crash dump was written to: erl_crash.dump init terminating in do_boot ()



Comments (5)

  1. Fred T-H repo owner

    To me that looks like a bug in the markdown library I use, based on a failing regex call when figuring out e-mails.

    Is there any file in your stuff that uses markdown syntax for e-mails that you could remove/add to confirm the issue? If I remember my re errors, the problem would be their regex string itself.

    If it's the case, they may already have fixed it and we'd just need to update the markdown lib dependency.

  2. Allen McPherson

    Thanks for the rapid reply, Fred. The failure was actually on compiling your demo-blog. I will mess around with those files and see if I can find markdown emails to remove. You'll probably find the problem sooner, but it'll be good experience to look through the files.

  3. Fred T-H repo owner

    It was indeed a fix in the regex from markdown. The faulty part was the "a-za-Z" in it, where a-Z is an invalid range given Z is greater than a. I've never seen this error because I hadn't re-built the app since then and the bug was introduced, then fixed (in a new repo) in the mean time.

    I've just updated dependencies and now things appear to work fine. Let me know if it fixed things for you.

  4. Log in to comment