weavenet
weavenet
Currently heirloom will delete buckets when it tears down an heirloom. If there are any objects in the buckets, they will not be deleted. However, if another heirloom has been...
Catch internal errors and log error message: Excon::Errors::InternalServerError /Users/bweaver/.rvm/gems/ruby-1.9.3-p385@simple_deploy_example/gems/excon-0.20.0/lib/excon/middlewares/expects.rb:10:in `response_call': Expected(200) Actual(500 InternalServerError) (Excon::Errors::InternalServerError) request => {:chunk_size=>1048576, :connect_timeout=>60, :headers=>{"Content-Type"=>"application/x-www-form-urlencoded; charset=utf-8", "Host"=>"sdb.u s-west-1.amazonaws.com:443", "Content-Length"=>215}, :idempotent=>true, :instrumentor_name=>"excon", :middlewares=>[Excon::Middleware::Expects, Excon:: Middleware::Idempotent, Excon::Middleware::Instrumentor, Excon::Middleware::Mock],...
2012-12-19 10:35:13 -0800 DEBUG : Executing: `heirloom upload -d ./chef-repo -n ericapp-chef-repo -i v1.0.0 -s mysecretpassword` /usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/heirloom-0.10.0/lib/heirloom/utils/file.rb:21: warning: Insecure world writable dir /Users/emiller/Documents in PATH, mode 040777
When performing a setup of multiple heirloom which use the same region / bucket prefix, I've occassionally seen the below error. /Users/bweaver/.rvm/gems/ruby-1.9.3-p327@composer/gems/excon-0.16.10/lib/excon/con nection.rb:292:in `request_kernel': Expected(204) Actual(409 Conflict) (Excon: :Errors::Conflict) request...
this is a fairly common occurance and can provide for a improved user experience if inside the application. /usr/local/rvm/gems/ruby-2.0.0-p353@sts/gems/simple_deploy-0.8.0/lib/simple_deploy/aws/cloud_formation/error.rb:22:in `process': Throttling => Rate exceeded (SimpleDeploy::Exceptions::CloudFormationError) from /usr/local/rvm/gems/ruby-2.0.0-p353@sts/gems/simple_deploy-0.8.0/lib/simple_deploy/aws/cloud_formation.rb:45:in`rescue in describe_stack' from...
Cloud Formation has a very sensitive rate limit for their API. We should not fail a build, but sleep and exponentially backoff when these errors are hit: 2013-02-18 08:39:34 -0800...
@bradly receieved a transient error than did not appear to be handled correctly. We should verify that our error handling logic is sound. 2013-05-21 19:22:21 -0700 INFO : Updating Cloud...