This issue: https://sentry.softwareheritage.org/share/issue/03c048c63f204b64bfcd9c26fa4f112e/ should have returned a 500 error, which should have raised an error on the client side (which is also the journal-client); but I do not see that error in Sentry, so it looks like the journal client was not configured to report that error to Sentry.

This should also have crashed the client process, but I do not see it logged in #swh-sysadm