[urgent] Fix for authenticate_pools and logout_pools

[solisoft]

It was missing @manager. before the pools variable ...
Right now, it's not possible to use replica-set with authentification.

[jonson]

I just ran into the same prob, 1.7.0 crashes immediately when trying to authenticate using a ReplSetConnection.

[solisoft]

Do you plan to release a new gem version ? It's just unusable right now with replicaset and authentification !!

[TylerBrock]

Yes, 1.8.0 is due out soon.

[parrish]

Just got burned by this in production.
Please pull the version or release a minor version!

[solisoft]

@parrish if you can, you can use moped until it's released ... http://mongoid.org/en/moped/ but it's mongoid only...
And yes, a minor version will be welcome ... but I think that all my next projects will use moped because of this kind of delay (which is not acceptable)

Another solution, you can fork it, create your own gem ...

[TylerBrock]

I'm sorry this has been delayed. I promise we are doing as much as humanly possible to get this out with the engineering time we have. However, if you are using mongoid I would also recommend updating and using moped.

I can try to cut 1.7.1 tonight when I get home but if you are having trouble just use the older gem. We all know how to use Gem files and 1.7 adds no new features that you can't get another way via 1.6.X.

Thanks for bringing this to our attention. Perhaps @brandonblack can push 1.7.1 today before I get home.

[parrish]

@TylerBrock with the engineering time we have

I know how that goes. I was honestly just concerned about having a known issue this serious in a release. I've reverted to a stable version, but I generally expect a release to be stable.

I'm advocating that the broken gem version be pulled from rubygems so other people won't be affected.

[brndnblck]

Quite simply, this just fell between the cracks and we totally dropped the ball.

We've been so focused on our 1.8.0 release which has some substantial changes (due out early next week) that this important fix just got lost in the fray. I'll be cutting a new 1.7.1 release that includes this fix in just a little while.

Again, our apologies for letting this slip out of our focus. We have a few new team members supporting the ruby driver now (myself included). We have big plans, major improvements scheduled, and our goal is to release/iterate a lot more often than we have been doing.

I'll post back here in a little while when this is available on rubygems. Stay tuned.