ruaok: there are a bunch of sentry errors like https://sentry.metabrainz.org/metabrainz/listenbr… from the mbid_mapping_writer. The stacktraces are getting truncated so we won't be able to know the exact errors. I looked into this and it seems to because of using at a few places `traceback.format_exc`, https://forum.sentry.io/t/some-stack-traces-are-t… mentions that this can lead to truncating the
2021-05-08 12831, 2021
_lucifer
stacktrace. alternatively, it is not possible to replace this usage, we can look into increasing the limit of string length reported by sentry.
2021-05-08 12818, 2021
killme joined the channel
2021-05-08 12857, 2021
ruaok
_lucifer: oh, interesting. an incorrect cron job ran and borked the underlying DB. fun.
2021-05-08 12809, 2021
ruaok
the place where the exception gets reported is here:
getting exceptions from the futures stuff was a pain...
2021-05-08 12842, 2021
_lucifer
ruaok, oh! i had seen that line but the line numbers in the stack trace didn't match so i was confused. the mismatch is probably because this is async code i guess.
2021-05-08 12855, 2021
ruaok
background threads, yes.
2021-05-08 12841, 2021
_lucifer
can we do logger.error(exc) there, does that eat up some info?
2021-05-08 12854, 2021
_lucifer
*, or
2021-05-08 12820, 2021
ruaok
I can try that. let me fix the underlying problem.
[bookbrainz-site] dependabot[bot] opened pull request #627 (master…dependabot/npm_and_yarn/hosted-git-info-2.8.9): chore(deps): bump hosted-git-info from 2.7.1 to 2.8.9 https://github.com/bookbrainz/bookbrainz-site/pul…
