Open sentry-io[bot] opened 9 months ago
Sentry issue: COURTLISTENER-6HM
We're getting a lot of these all of a sudden??
Sentry issue: COURTLISTENER-6HH
Sentry issue: COURTLISTENER-6J7
This is happening because I added a logger.error call on pacer/email/_parse_bankruptcy_short_description .
This function requires an explicit if
clause for each bankruptcy court, and we only have cases for 6, so we are not parsing "short descrition" field for the courts in these sentry issues.
Mostly all we have is the logger, no stacktrace
This missing data does not trigger an exception since short_description
is not a required field, but it is a data quality problem. The short_description
data point is (probably) available but we are not picking it up, and without an explicit logger call, it would go unnoticed forever
Got it, so we'll need to reevaluate this code 200 times as each court comes up. Yikes, but I guess that's sort of OK. Can you take a look at the auto-assign rules in Sentry and make it so that it comes to you? When I see these messages in Sentry, they don't have code traces, so it's hard for me to even know if the code is in Juriscraper/CL/Courts-db, etc.
Sentry issue: COURTLISTENER-6M2
pamb
Sentry Issue: COURTLISTENER-6Z1
For court mdb
Sentry Issue: COURTLISTENER-73D
For court deb
Filed by @grossir
I mixed up a Sentry issue that belongs here, and had sent it over to #914
Sentry Issue: COURTLISTENER-7PN
Court txnb
Filed by @grossir
Sentry Issue: COURTLISTENER-7W4
Filed by @grossir
Sentry Issue: COURTLISTENER-7W3
Filed by @grossir
Sentry Issue: COURTLISTENER-844
For arwb
Filed by @grossir
I'm not sure on this one if it's a Juriscraper thing. Mostly all we have is the logger, no stacktrace, so we need to figure out why we're logging this as an error and either fix the data (?) error or tune down the log message.
Filed by @mlissner
Sentry Issue: COURTLISTENER-6HS