Alberto Islas

We continue experiencing `ConflictErrors` as you can see in [COURTLISTENER-5V5](https://freelawproject.sentry.io/issues/4745888344/) I downloaded and triaged the events from the last two months (since the last time we checked them) to review...

Correct, the errors described here came from the extension, similar to the previous data integrity issues that originated in Juriscraper. We're only taking advantage of the ES `ConflictError` to discover...

Yeah, that sounds good. Most of the errors triggered here do not prevent the data from being up to date in Elasticsearch. This is because if a `ConflictError` occurs, it...

These are the parsing differences described in [#3143 ](https://github.com/freelawproject/courtlistener/issues/3143#issuecomment-1984535707) related to `FreeOpinionReport` Opinions Report:  Docket Report:  For instance,...

> That'd take care of this source of issues, right? Yeah, I've already create the related issues for these fixes so you can prioritize them accordingly.

Thanks @jordanparker6 for the work on this. Here is some feedback: ### **Triggering Webhooks** Your current webhook triggering logic resides within custom `save` and `delete` model methods. Here are some...

Here you can find more details about how the field tracker works, in case we decide to go with this approach: If you look at the `OpinionCluster` or `Opinion` models,...

> I am a bit worried about celery tasks piling up though, and about our ability to cancel celery tasks if an endpoint is down. @albertisfu, do you recall how...

Correct, I think we'll be fine. Celery tasks won't pile up if an endpoint goes down. The task will be able to handle that gracefully while finishing sending all the...

> @albertisfu I have the daemon stuff up. Still lacking a good way to test this though. > Is that along the lines of what you had in mind? @jordanparker6...