-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not send "Select a Person" page to CL #362
Comments
I think this is not a CaseQuery page. Case Query pages have a table-like "header", and the erroring document has not. From the test cases, 2 examples of CaseQuery pages: This HTML page (s3) seems like a Case Query Advanced, specifically a "Parties" page. juriscraper is not prepared to parse this yet. But, apart from that, CL called the wrong parser (EDIT: I see that we do not support this kind of pages yet)
|
OK, so this is more of a RECAP extension bug. We shouldn't be sending the "Select a Person" page to CL in the first place. If it were a useful page, I'd say we should add support for it, but since it's not, yeah, we can just make sure the extension doesn't send it. I'll refile this issue over in the recap repo. |
I think this is a parse failure for a PACER docket. Can we take a look and see if a tweak makes sense?
Sentry Issue: COURTLISTENER-5DS
The text was updated successfully, but these errors were encountered: