Ernestas Monkevicius

https://github.com/deivid-rodriguez/byebug/issues/179#issuecomment-152727003

Cool. I'll try to get those running and see.

So the the motion-demos start up quick for me, in a few seconds as normal. But my own project takes minutes.

I'm a long time lurker, first time issue poster on Github, so I'll give it a try :D I just basically fork my own project repo and strip out as...

So good news is my start up time is quick again. Bad news is I don't know what the issue was. All I did was pull down my own repo...

Seems like a good theory, especially as the repo doesn't have the tmp folder and neither does the new project folder. But I've deleted tmp and it didn't seem improve...

That's interesting. At first I thought that was gonna be the issue too. Originally I was running ruby 2.6.3 with rails ~> 6.0. When I pulled down the motion-demos and...

Ok so w.e. is going, must be motion related. I just did what @spencersteiner just said, comment out the motion initializer in the old project and now it's booting in...

Can confirm, that fixes it @alecdotninja but then the real question is, why does pulling down the same repo and without setting config.revision in motion initializer still work as well...

So setting ```config.revision = `git rev-parse HEAD`.chomp``` is prefered if using git then?