You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2018. It is now read-only.
At random points, I get a ECONNRESET issue, and truly I don't know how to save the error and kept trying until it saves the file, this is the exception:
/usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:199:in write': Connection reset by peer (Errno::ECONNRESET) from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:199:inwrite0'
from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:173:in block in write' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:190:inwriting'
from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:172:in write' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1937:insend_request_with_body'
from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1919:in exec' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1317:inblock in transport_request'
from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1316:in catch' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1316:intransport_request'
from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1293:in request' from /u/apps/s3_rabbit/shared/bundle/ruby/1.9.1/gems/uber-s3-0.2.4/lib/uber-s3/connection/net_http.rb:25:inrequest'
from /u/apps/s3_rabbit/shared/bundle/ruby/1.9.1/gems/uber-s3-0.2.4/lib/uber-s3/connection.rb:52:in block (2 levels) in <class:Adapter>' from /u/apps/s3_rabbit/shared/bundle/ruby/1.9.1/gems/uber-s3-0.2.4/lib/uber-s3/object.rb:94:insave'
from s3_rabbit.rb:30:in `block (3 levels) in
Also, for some reason, I cannot write files with spaces on its name, but this is acceptable by Amazon S3 (to reproduce, just use the gem and try to write a file with a space)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At random points, I get a ECONNRESET issue, and truly I don't know how to save the error and kept trying until it saves the file, this is the exception:
/usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:199:in
'write': Connection reset by peer (Errno::ECONNRESET) from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:199:in
write0'from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:173:in
block in write' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:190:in
writing'from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/protocol.rb:172:in
write' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1937:in
send_request_with_body'from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1919:in
exec' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1317:in
block in transport_request'from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1316:in
catch' from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1316:in
transport_request'from /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/http.rb:1293:in
request' from /u/apps/s3_rabbit/shared/bundle/ruby/1.9.1/gems/uber-s3-0.2.4/lib/uber-s3/connection/net_http.rb:25:in
request'from /u/apps/s3_rabbit/shared/bundle/ruby/1.9.1/gems/uber-s3-0.2.4/lib/uber-s3/connection.rb:52:in
block (2 levels) in <class:Adapter>' from /u/apps/s3_rabbit/shared/bundle/ruby/1.9.1/gems/uber-s3-0.2.4/lib/uber-s3/object.rb:94:in
save'from s3_rabbit.rb:30:in `block (3 levels) in
Demo code: https://gist.github.com/rorra/5216306
Also, for some reason, I cannot write files with spaces on its name, but this is acceptable by Amazon S3 (to reproduce, just use the gem and try to write a file with a space)
The text was updated successfully, but these errors were encountered: