create_access_key for username failing.. excon error?

[hh]

% rvm use 1.9.2@fog --create
Using /Users/codecafe/.rvm/gems/ruby-1.9.2-p180 with gemset fog

% gem install fog

% gem list

*** LOCAL GEMS ***

builder (3.0.0)
excon (0.6.0)
fog (0.7.1)
formatador (0.1.2)
json (1.5.1)
mime-types (1.16)
net-ssh (2.1.3)
nokogiri (1.4.4)
rake (0.8.7)
ruby-hmac (0.4.0)

% irb

require 'fog'

new_username = 'myusername'

bucket_name = 'mybucket'

aws_credentials = {
:aws_access_key_id => 'XXXCXCATATTETT',
:aws_secret_access_key => 'loremipsumgratisforumquorum',
}

iam = Fog::AWS::IAM.new(aws_credentials)

user_response = iam.create_user(new_username)

key_response = iam.create_access_key('UserName' => new_username)

Excon::Errors::SocketError: wrong number of arguments (3 for 1)
from /Users/codecafe/.rvm/gems/ruby-1.9.2-p180@fog/gems/fog-0.7.1/lib/fog/core/connection.rb:16:in block in request' from /Users/codecafe/.rvm/gems/ruby-1.9.2-p180@fog/gems/excon-0.6.0/lib/excon/response.rb:47:inparse'
from /Users/codecafe/.rvm/gems/ruby-1.9.2-p180@fog/gems/excon-0.6.0/lib/excon/connection.rb:140:in request' from /Users/codecafe/.rvm/gems/ruby-1.9.2-p180@fog/gems/fog-0.7.1/lib/fog/core/connection.rb:20:inrequest'
from /Users/codecafe/.rvm/gems/ruby-1.9.2-p180@fog/gems/fog-0.7.1/lib/fog/aws/iam.rb:106:in request' from /Users/codecafe/.rvm/gems/ruby-1.9.2-p180@fog/gems/fog-0.7.1/lib/fog/aws/requests/iam/create_access_key.rb:31:increate_access_key'
from (irb):12
from /Users/codecafe/.rvm/rubies/ruby-1.9.2-p180/bin/irb:16:in `

'

[geemus]

I'll try to get this fixed soon, but somebody else said they had a similar problem and were able to get around it by reverting to an earlier version of excon. Just thought I would point that out so you could have a work around until I can get it sorted out.

[geemus]

fix push parser block passed to excon

excon was updated to allow for tracking progress, and though we are not
using this feature we still need to acknowledge the change in the params
that are passed back to blocks for requests.

Closed by ab3e04b
Closed by ab3e04b

[geemus]

I believe this is fixed in 0.7.2