Christopher Corley

:point_right: _poke_ any update on a new release, @minad?

Ah, makes sense. Fair enough. Thanks for the tip!

Also, thanks for making this open source and keeping things like the tagged versions/branches available. :+1:

You may be right about it being related to actual framerate and not network. I also have tested this by just laying down a `sleep 3s` (e.g. dumb cap to...

@sebcrozet I am ready for this to be reviewed. I selected the feature flag for this purpose because it makes the `for ... x.iter()` simpler to write in Rust without...

Also facing this issue trying to update to v5.4.0 from v5.3.0. For anyone using ClickOnce, you can bypass this be following these instructions: http://stackoverflow.com/a/721350/615429

@antonpup no, sorry. Kind of gave up and moved on.

Ah, yes, you are right. I was testing this on a different branch and added all of the feature checks after-the-fact and was not working against the correct branch. My...

I ran into a similar issue, setting `heroku buildpacks:set https://github.com/emk/heroku-buildpack-rust`, but instead my build now silently produces this line, and then fails the release step (`/bin/sh: 1: ./target/release/diesel: not found`):...

Not sure about the buildpack publishing, as I've never done it, but it doesn't seem to be automatic going by this notice on the docs: https://devcenter.heroku.com/articles/buildpack-registry#publishing-a-buildpack-version Seems that the convention...