Pinned Disk IO v0.34.0

[NeoKactus]

I tried upgrading from v0.33.9 to v0.34.0 and noticed that my deployment time tripled due to disk IO.
The disk IO is being pinned by chown -R herokuishuser:herokuishuser /app. I am assuming it's trying to chown node_modules on our HDDs.

I still need to play around with the issue, but for now we downgraded to v0.33.9. Is there something I am missing from the migration guide or should I file a bug report with additional info?

Side question. Is it practical/feasible to setup a ramdisk for the Dokku build process?

[josegonzalez]

I think this was caused by a failure to release the herokuish repo, which is currently blocked by a bug. I'm investigating a fix now and will report back. Thanks for raising this!

[josegonzalez]

This change should also help a bit: https://github.com/gliderlabs/herokuish/pull/1173/files

That said, I think I might also need to place that behind the same check, so we'll see how it impacts things.

[josegonzalez]

@NeoKactus this should be fixed now if you upgrade to at least Herokuish 0.8.0 and Dokku 0.34.1.

[NeoKactus]

Ty that has fixed it!