Mike Lissner

Our retries and moving to a single worker might be helping here, errors are down. If that doesn't work, the next options are to: 1. Set up the kube-proxy to...

@albertisfu can you chime in about whether we're still seeing errors with connections to doctor, please?

Looks like even with five retries we still get this from time to time. I think it's worth looking at the k8s config for doctor and seeing if we're missing...

Actually, @albertisfu says the latest changes haven't been deployed, so let's check in here again after those are deployed.

@albertisfu can you check again and give an opinion about whether this seems fixed to you?

> [29702374](https://www.courtlistener.com/docket/7004943/108/united-states-v-madrid-paz/): This one is weird, the extraction succeeded but seems that the content returned doesn't match the actual content. Is this normal? That's due to https://github.com/freelawproject/doctor/issues/139 > Here we...

All suggestions make sense to me. Thank you for your analysis here.

Can you pull out the pep8 stuff in a separate PR? I'm afraid I'll miss something with it all mixed together like this.

This is worth doing, yes, but I don't know where we'll prioritize it. If John does it, we'll merge it, but I don't think it's high on our list otherwise.

Grr, docket numbers are a pain. We'll want to deal with this, I suppose, at least in the docket number search box. Thanks.