Michael Kirk

@PayasR - #366 was opened a while ago. I've just left some comments there to see if they're still interested in getting their implementation merged - it's been a while.

Fair question. I think finding shortest path is a likely problem for someone doing other stuff with the geo crate, so it makes sense to make it easy for people...

I hit this too. I'm not sure yet what's causing it, but here are some notes: First, I commented out the line that deletes the raw dtrace dump: ```patch @@...

I'm also on a mac btw (10.15) $ dtrace -V dtrace: Sun D 1.15 Is anyone hitting this *not* on a mac?

I have a workaround at https://github.com/flamegraph-rs/flamegraph/pull/101, it would be interesting if anyone who frequently experiences this error could give it a whirl.

Assuming it's a bug that dtrace ever outputs invalid utf-8, I filed a radar (rdar://8800290) and duped to open radar here: https://openradar.appspot.com/radar?id=5013532726788096

> im unable to test it cause theres no release post 0.3.2 I too would like to see a new release. =) But in the meanwhile, in case you weren't...

> so is this still desirable to add to the lib? I don't personally have a use case for anything other than f64 geojson, but maybe other folks do. I'll...

I'm hitting an identical looking error with a planet build, and similarly, everything seems to work fine with the smaller portland build. Given the long time it takes before the...

> I'm hitting an identical looking error with a planet build, and similarly, everything seems to work fine with the smaller portland build. > > Given the long time it...