Jack Cushman

Once this is done we can also stop setting `disambiguate = True` in `get_frontend_url`: ``` if not m: # if cite doesn't match the expected format, always disambiguate so URL...

I think what we want to do here is add a denormalized `volume_out_of_scope` field to `CaseMetadata` that contains a copy of `case.volume.out_of_scope`, so we can efficiently update `case.in_scope` without loading...

Oh, this was produced with: ``` select cite_from.frontend_url, cite_from.id, cite_from.decision_date_original, ec.normalized_cite, cite_to.frontend_url, cite_to.id, cite_to.decision_date_original from capdb_casemetadata cite_from inner join capdb_extractedcitation ec on cite_from.id = ec.cited_by_id inner join capdb_citation cite on...

It might be helpful to find a scanned PDF with OCRed text that we didn't create, and see if that one works differently in Firefox -- I'm not clear if...

Hi, @jon-freed! Thanks for this report. To confirm, it looks like CAP doesn't have data from the "Appeals Not Accepted for Review" subsection of the "Orders Announced" appendix to Ohio...

This is a nice clean example where the footnote mark `1` appears in a different opinion section than the footnote text labeled `1`, and the footnote text just wants to...

We are currently hit or miss on whether `` is included in case XML output -- it depends whether sync_case_body_cache has been run since this fix landed for a given...

For examples of projects supporting or switching to vectorscan, here's the PR [switching ClickHouse to vectorscan](https://github.com/ClickHouse/ClickHouse/pull/38171), and here's the [commit](https://github.com/gliwka/hyperscan-java-native/commit/ad0493060f9ef8581106716174877ff9ec2d8b9e) and [related issue](https://github.com/gliwka/hyperscan-java/issues/128) adding vectorscan as a platform option for...

The underlying problem here is being discussed over at #458. As a workaround, I'm doing this to import waypoints in webpack: `require('waypoints/lib/jquery.waypoints.js');` I'm new to webpack but I _think_ your...

@erikrose: > Adding an --almost-require-hashes option or similar. Seems okay on the face of it. How about a special --hash value, like: ``` # accept the hash value provided in...