Mike Lissner comments

Results 1710 comments of


                                            Mike Lissner

feat(alerts): Sort dockets on the Docket Alert page by last hit

> But I don't see any mechanism for partitioning ES and Redis, so it looks like there is just a hope that tests won't clobber each others' data. Maybe there...

feat(alerts): Sort dockets on the Docket Alert page by last hit

Weird error about secrets, Elisa. We use AWS secrets. Maybe Docker has secrets too? Sort of seems like their server's fault though, on that one?

feat(alerts): Sort dockets on the Docket Alert page by last hit

I don't think we pull secrets from AWS during build/test. I think these are coming from Github's secrets tool, maybe? The errors at the top of that log are from...

fix(docket_number_raw): use docket_number_raw as param instead of docket_number

I just flagged Alberto as a reviewer because some of this PACER code is pretty gnarly. Probably good to have somebody from each team take a look.

fix(docket_number_raw): use docket_number_raw as param instead of docket_number

@grossir I just noticed this is marked as blocked on the Web sprint team. Is that right?

fix(docket_number_raw): use docket_number_raw as param instead of docket_number

@grossir this ticket is cross listed on the Web team, so I thought I'd ask if it's a good time to move it forward on your side?

6561 Ingest SCOTUS Docket lower court data

> If you agree, I can open a follow-up PR to implement docket-number cleaning for OriginatingCourtInformation to handle the remaining 1%. That makes sense, yes. Can you please include your...

WALWrite LWLock contention

That sounds good to me. It's easy to do, IIRC. What percentage do you think we should go for?

WALWrite LWLock contention

All set.

WALWrite LWLock contention

I feel like the takeaway for me is that when the DB's disk gets overloaded, we can expect something to herniate, and in this case it was the search query...