Problem: many messages fail to parse

[athos]

Hi, there 😃

I ran into an error when trying to access the following page:

• https://clojurians-log.clojureverse.org/clojurescript/2018-11-13

The error looks as follows:

I'm suspecting this post on that day is causing it, which includes some strikethrough in a quote.

[plexus]

This page is still erroring out. It would be great if in general we could

• wrap the parsing in a try/catch, and render the raw message when parsing fails
• log the message somewhere, so we can go through them systematically later.

[plexus]

@dawran6 how would you feel about trying your hand at this one. At the point where each message gets parsed and converted from markdown to hiccup we should wrap it in a try/catch, and in the catch just return the message unparsed, plus put a println, "Failed to parse message ..."

[dawranliou]

Absolutely, I'm working on this. Is println the current preferred way of logging?

[plexus]

Yeah println is fine, we log the stdout of the process. I don't think there's any more proper logging in place yet

[plexus]

Pages that errored before according to google search console:

https://gist.github.com/90d310374bcdf234bfe4ea5cfb84da1d

Now that we no longer fail completely on parser errors we can look at those pages, find the messages that don't render, and add test cases for them (and then fix the parser :) )