Austin Gill

An alternative approach I've used for this problem is to define a custom rule ```python import re from gitlint.rules import BodyMaxLineLength class BodyMaxLineLengthWithExceptions(BodyMaxLineLength): name = "body-max-line-length-with-exceptions" id = "UC1" def...

I wonder if this is related to https://github.com/rust-lang/cmake-rs/issues/172? I expect #172 is caused by the caveat mentioned in https://docs.rs/jobserver/latest/jobserver/struct.Client.html#method.from_env about `from_env` being unsafe to call twice in the same process...

I'm now convinced this is a cc-rs issue. Using binary search, I was able to narrow it down to the 1.0.42 release of cc-rs, which is the release that first...

I think `re.sub(r',\s*)', ')')` or equivalent will be sufficient, as long as it doesn't tank performance. Otherwise, filter through `sed` as necessary.

It appears there's already a BEZIERCURVE WKT extension: https://crates.io/crates/beziercurve-wkt

Here are more test cases :cry: [example-9-after.txt](https://github.com/Notgnoshi/generative/files/6331953/example-9-after.txt) [example-9-before.txt](https://github.com/Notgnoshi/generative/files/6331954/example-9-before.txt) [example-10-after.txt](https://github.com/Notgnoshi/generative/files/6331955/example-10-after.txt) [example-10-before.txt](https://github.com/Notgnoshi/generative/files/6331956/example-10-before.txt)

Here's another problem. Given a graph: ``` 0 POINT(0 0) 1 POINT(1 0) 2 POINT(2 0) 3 POINT(3 0) 4 POINT(0 1) 5 POINT(1 1) 6 POINT(2 1) 7 POINT(3...

First step - try updating to a recent Geos release? It appears to be a bug in the Polygonizer, and not in the graph parsing...

> First step - try updating to a recent Geos release? It appears to be a bug in the Polygonizer, and not in the graph parsing... https://github.com/Notgnoshi/generative/pull/154 does _not_ fix...

This is still an issue with #166