Ryan Smith
Ryan Smith
Yes. A forking worker is absolutely supposed to work on 3.0.0. The fact that it is not is a bug.
@2468ben Do you think we could fix the issue without creating a connection pool? Is there a simpler fix? Also, to my knowledge, there isn't any active development on this...
As I alluded in a [tweet](https://twitter.com/ryandotsmith/status/421030545154269184), you can almost do this today. ``` ruby worker = QC::Worker.new QC.count.times {woerker.work} ``` The problem is that `QC::Worker#work` spins on the worker's `@running`...
Great point. If we had the right primitives, we could easily wrap them up into a QC provided Rake task.
Hello. I suspect this bug still exists in the project. I have given this type of problem a lot of thought over the years through my experiences with [queue_classic](https://github.com/ryandotsmith/queue_classic); so...
I will also say that if @thisandagain is interested in this direction, I would be more than happy to start working on a pull request.
[What the Mean Really Means](http://dtrace.org/blogs/brendan/2013/07/12/what-the-mean-really-means/) - Brendan Gregg
Looks neat! If it can be something that is optionally added by the buildback user, then I would accept a PR.
It could be. I used https://buildkits.herokuapp.com/ to make the tarball. I had some strange issues with the build-kits service. I may just use a personal S3 bucket to host the...
Hello, @eprothro Sorry for the delayed response. This week was incredibly busy for me. Anyways, you raise some really interesting questions. Lets try and tease them apart to gain a...