a few days ago I started to see
Would have removed best_in_place (2.0.2)
Would have removed thor (0.16.0)
in my heroku deploy output.
It used to say that it removed the gem.
anyone know what's up with that?
update
heroku updated to latest ruby 1.9.3 and bundler cache cleaned fine.
Heroku lets you deploy, run and manage applications written in Ruby, Node. js, Java, Python, Clojure, Scala, Go and PHP.
Free Services on HerokuHeroku offers a free plan to help you learn and get started on the platform. Heroku Buttons and Buildpacks are free, and many Heroku Add-ons also offer a free plan. Experiment easily with different technologies to discover what works best for you and your apps.
If you wish to stop a running one-off dyno, use heroku ps:stop with its name. A one-off dyno will not stop if you issue heroku ps:restart on your application.
That's a bug in Heroku deployment configuration. It writes a file .bundle/config which has a line:
BUNDLE_DRY_RUN: false
When bundler loads this global config file, it translates this to :dry_run => "false" When it checks for this setting, it's checking settings[:dry_run], which is a string, which evaluates to true.
You can remove this line by some shell commands (heroku run bash):
mv -f .bundle/config .bundle/config.orig
sed '/BUNDLE_DRY_RUN/d' < .bundle/config.orig > .bundle/config
And then run
bundle clean
This is a bug in the bundler gem – essentially extra debugging info is being dumped to the screen. It should be patched in the next release. The removal would be from a cache, most likely because a newer version is available (latest best_in_place
is 2.0.3, Thor
0.17.0). These can be safely ignored.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With