Open bzz opened 2 years ago
Right now on parsing the papers we only count all errors, silently skipping failures and thus hiding their root cause. https://github.com/bzz/scholar-alert-digest/blob/7d2e4de957edf2864360a95b579fc919e9fd561f/papers/papers.go#L46-L48
This leads to difficulties reproducing bugs like #76 as one needs to modify source code (by adding log.Print(err) to https://github.com/bzz/scholar-alert-digest/blob/7d2e4de957edf2864360a95b579fc919e9fd561f/papers/papers.go#L83-L84) for debugging.
log.Print(err)
Instead, it would be nice to have:
-v
map[Subject][]error
That would simplify the debugging, as users would be able to identify the offender emails and attach the specific HTMLs that causes errors.
Right now on parsing the papers we only count all errors, silently skipping failures and thus hiding their root cause. https://github.com/bzz/scholar-alert-digest/blob/7d2e4de957edf2864360a95b579fc919e9fd561f/papers/papers.go#L46-L48
This leads to difficulties reproducing bugs like #76 as one needs to modify source code (by adding
log.Print(err)to https://github.com/bzz/scholar-alert-digest/blob/7d2e4de957edf2864360a95b579fc919e9fd561f/papers/papers.go#L83-L84) for debugging.Instead, it would be nice to have:
-vflag that would print all the errorsmap[Subject][]error) through paper parsing, as part of StatsThat would simplify the debugging, as users would be able to identify the offender emails and attach the specific HTMLs that causes errors.