Dave Myron
Dave Myron
I'm having the same issue. Versions: ruby: 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.6.0] gem: 1.8.6 rvm: 1.6.31 enginex: 0.8.1 The "already activated" error only seems to show up in a project...
@cmeiklejohn: The temporary workaround is to edit the local enginex gemspec. Should be at `.rvm/gems//specifications/enginex-0.8.1.gemspec` – If you change the gemspec to use `~> 3.0.9` then it'll work for now.
I can't _prove_ that, but I went through various projects testing the command and that was a common feature of those that failed. However... today's a new day... and I'm...
And *I'd* like a similar thing, except I want to align on the space *after* the comma (leaving the comma where it is).
Interesting find. Does it also go away if you use a thread_number larger than 1?
@nesquena Should we update the CI config to drop
What worker are you using, @hari-151191? The retry_limit is only used by the ThreadsOnFork worker according to the docs.
@forresty Can you rebase this to the current master?
@forresty – crazy that it's been more than a year. Care to rebase against the current master?