Jonathan Hawkes

[2020-07-18T07_38_21_727Z-debug.log](https://github.com/sindresorhus/np/files/4941309/2020-07-18T07_38_21_727Z-debug.log) This is still happening. And bug #427 references this issue as well.

This issue is related to PR #22075, which sought to fix issue #22074.

> @techhead but that is already merged 2 weeks ago? I am running mastodon main from yesterday. Yes, I understand that. What I'm saying is that part of my fix...

Pull request #22075 fixes this.

I spent an embarrassing amount of time on this, especially figuring out the first part, why the `yarn install` was hanging. There don't seem to be many others who have...

After Vangrant moved successfully past the `yarn install`, `vagrant up` seemed to complete successfully. ``` To start server $ vagrant ssh -c "cd /vagrant && foreman start" ``` But when...

PR #22075 was merged. So this issue should be resolved.

Pull request #22075 fixes this.

The glitch by which you are forced to install gems `bundler` and `foreman` twice was apparently related to the way in which `rvm` was being installed. To alter, I followed...

> Nice find. Thanks for the upgrade. > > Could you replace `cd /vagrant && foreman start` with `foreman start -d /vagrant` in your PR? Was going to, but I...