I haven't installed any gems since the last time I deployed, but
Heroku keeps thinking there is something new I suppose, and that
significantly slows down my deployment time. How can I make sure that
I don't get this message?
EDIT:
This is from my deployment message. I dunno...is it normal?
Writing objects: 100% (13/13), 1.88 KiB, done.
Total 13 (delta 10), reused 0 (delta 0)
-----> Heroku receiving push
-----> Rails app detected
-----> Detected Rails is not set to serve static_assets
Installing rails3_serve_static_assets... done
-----> Gemfile detected, running Bundler version 1.0.7
Unresolved dependencies detected; Installing...
Using --without test:development:staging
Fetching source index for http://rubygems.org/
$ git add Gemfile.lock
$ git commit -m "We should always check in Gemfile.lock in our applications."
$ git push heroku master
I contacted support and they resolved it.
Related
I'm currently using Raspberry Pi 3 with the newest Raspbian Buster version. I followed the installation guide here:
https://hyperledger-fabric.readthedocs.io/en/release-1.4/install.html
and installed all the prerequisites beforehand: curl, docker, docker-compose, go, python, nodejs.
But the moment I run the fabric-samples installation command:
curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap.sh | bash -s
I encounter the following error:
Clone hyperledger/fabric-samples repo
===> Cloning hyperledger/fabric-samples repo and checkout v2.0.0
Cloning into 'fabric-samples'...
remote: Enumerating objects: 19, done.
remote: Counting objects: 100% (19/19), done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 4685 (delta 4), reused 7 (delta 1), pack-reused 4666
Receiving objects: 100% (4685/4685), 1.67 MiB | 193.00 KiB/s, done.
Resolving deltas: 100% (2330/2330), done.
error: pathspec 'v2.0.0' did not match any file(s) known to git
Pull Hyperledger Fabric binaries
===> Downloading version 2.0.0 platform specific fabric binaries
===> Downloading: https://github.com/hyperledger/fabric/releases/download/v2.0.0/hyperledger-fabric-linux-armv7l-2.0.0.tar.gz
--2020-02-10 17:04:37-- https://github.com/hyperledger/fabric/releases/download/v2.0.0/hyperledger-fabric-linux-armv7l-2.0.0.tar.gz
Resolving github.com (github.com)... 13.229.188.59
Connecting to github.com (github.com)|13.229.188.59|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-02-10 17:04:37 ERROR 404: Not Found.
tar (child): hyperledger-fabric-linux-armv7l-2.0.0.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
rm: cannot remove 'hyperledger-fabric-linux-armv7l-2.0.0.tar.gz': No such file or directory
==> There was an error downloading the binary file.
------> 2.0.0 platform specific fabric binary is not available to download <----
It seems that the fabric binaries and images are unavailable for armv7 processors. Other answers such as this one show me how to build the fabric binaries and images manually, but I still don't know how to get the fabric-samples to run afterwards.
Does anyone know how to install Hyperledger Fabric on RPi such that I can run the samples like byfn and fabcar as smoothly as in the documentation?
Raspberry now has a 64bit OS which you will need to run Hyperledger Fabric (https://www.raspberrypi.org/forums/viewtopic.php?t=275370).
I have made the docker images for this OS already for my own project which you can find if you follow this repo https://github.com/SurfTheRepo/HLF-for-RPI-. If you clone the repo you will find the binaries for the 64bit OS in the bin folder. I have some links explaining how I built the images and binaries in the readme.
Everything is for HLF2.3 btw.
I have been able to run the test-network on my raspberry using this.
But my Raspberry Pi is a model 4 and is 8GB, I dont think it will be possible on a Pi3, (the RAM usuage goes up to about 4gb when I run the test-work).
Im still working on this project so I'm changing the repo pretty often, but you should be able to get a general idea of how it all works from it.
This is my first attempt to push a Rails v6.0.0 app to Heroku. The error msgs are:
Could not detect rake tasks
ensure you can run `$ bundle exec rake -P` against your app
and using the production group of your Gemfile.
Activating bundler (2.0.1) failed:
Could not find 'bundler' (2.0.1) required by your /tmp/build_94b6a9e04d812c465a5480f59429532e/Gemfile.lock.
To update to the latest version installed on your system, run `bundle update --bundler`.
To install the missing version, run `gem install bundler:2.0.1`
Checked in 'GEM_PATH=vendor/bundle/ruby/2.5.0', execute `gem env` for more information
To install the version of bundler this project requires, run `gem install bundler -v '2.0.1'`
I can run 'bundle exec rake -P', no problem.
I have verified that bundler 2.0.1 is installed, no problem.
Suggestions?
A similar bugreport on the bundler repo mentions that bundler 2.0.1 conflicts with heroku. I've copied the following fix instructions from that comment:
gem install bundler -v 2.0.2
bundle update --bundler
commit & push Gemfile.lock changes in your repo
deploy with git push heroku master
I am no longer able to push my app to Bluemix. I am using the swift_buildback for a Kitura app.
The last time I successfully pushed it, was yesterday. I noticed that the default buildpack is now 2.0.5. The last time I pay attention to that, it was 2.0.4. I don't know how to specify an older version of the buildpack, to rule out a problem there.
The cf push returns the following:
Downloading swift_buildpack...
Downloaded swift_buildpack
Creating container
Successfully created container
Downloading app package...
Downloaded app package (46.5M)
Downloading build artifacts cache...
Downloaded build artifacts cache (43.9M)
Staging...
-----> Buildpack version 2.0.5
-----> Default supported Swift version is 3.1
-----> Configure for apt-get installs...
-----> Writing profile script...
-----> Copying deb files to installation folder...
-----> No Aptfile found.
-----> Getting swift-3.0.2
-----> WARNING: Default supported Swift version: swift-3.1
-----> WARNING: Requested Swift version for your app: swift-3.0.2
Cached swift-3.0.2
-----> Unpacking swift-3.0.2.tar.gz
-----> Getting clang-3.8.0
Cached clang-3.8.0
-----> Unpacking clang-3.8.0.tar.xz
-----> .ssh directory and config file not found.
-----> Loading from cache:
-----> - Packages
-----> Fetching Swift packages and parsing Package.swift files...
-----> Additional packages to download: libcurl4-openssl-dev openssl libssl-dev
-----> libcurl4-openssl-dev is already installed.
-----> openssl is already installed.
-----> libssl-dev is already installed.
-----> No additional packages to download.
-----> Skipping installation of App Management (debug)
-----> Installing system level dependencies...
-----> Installing deb_files
dpkg-deb: error: failed to read archive `deb_files': No such file or directory
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223
Destroying container
FAILED
Error restarting application: BuildpackCompileFailed
In order to verify that your app works with the previous version of the buildpack, just add the -b <buildpack name> flag to your cf push command.
The names of the available buildpacks can be obtained by running cf buildpacks. In this case, since you want the old 2.0.4 buildpack version, the command will look like this:
cf push <app_name> -b swift_buildpack_v2_0_4-20170125-2344
The team that administers the Swift buildpack for Bluemix can help troubleshoot issues like this in their open Slack team - https://swift-at-ibm-slack.mybluemix.net.
I'm getting the following error when trying to fire up script/console for my rails 2.3.15 app, after upgrading from rails 2.3.5. Does this mean the issue is with bundler 1.2.1 is not compatible with rack 1.1.3? Any help would be appreciated immensely.
usr/lib/ruby/gems/1.8/gems/bundler-1.2.1/lib/bundler/rubygems_integration.rb:157:in gem': can't activate rack (~> 1.0.1), already activated rack-1.1.3. Make sure all dependencies are added to Gemfile. (Gem::LoadError)
from /home/developer/bigpink/vendor/rails/actionpack/lib/action_controller.rb:34
from /home/developer/bigpink/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:inrequire'
from /home/developer/bigpink/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in require'
from /home/developer/bigpink/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:innew_constants_in'
from /home/developer/bigpink/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in require'
from /home/developer/bigpink/vendor/rails/railties/lib/commands/server.rb:2
from script/server:3:inrequire'
from script/server:3
In my case, problem solved by the following steps:
Deleted the directory $PROJECT_ROOT/vendor/rails
Modified RAILS_GEM_VERSION in config/environment.rb
we used this process to upgrade Rails to 3.2.11 on our Heroku apps (as reported here)
stop – your Ruby on Rails (RoR) server
edit – appropriate line in gem file to read [one of]:
gem ‘rails’, ’3.2.11′
gem ‘rails’, ’3.1.10′
gem ‘rails’, ’3.0.19′
gem ‘rails’, ’2.3.15′
run – gem update
run – bundle update
run - bundle install
test – rspec # or test-driven dev’t framework of choice
launch – rails s
test – # interact with Rails server & explore if all is well
run – git add .
run – git commit -a -m “upgrade Rails server to ver. [x.y.z]“
run - git push # to github or rcs of choice
run - git push heroku # or to deployment server of choice
My deployment is stuck on fetching gem metadata from rubygems every time I deploy.
It worked this morning, had problems this afternoon and now it's not working again.
We tried from somewhere else and from other computers with the same result.
It works fine locally I can update from rubygems without a problem.
Visual:
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 764 bytes, done.
Total 9 (delta 7), reused 0 (delta 0)
-----> Heroku receiving push
-----> Ruby/Rails app detected
-----> Using Ruby version: ruby-1.9.3
-----> Installing dependencies using Bundler version 1.2.1
Running: bundle install --without development:test --path vendor/bundle --binstubs bin/
Updating https://github.com/epetre/negative-captcha.git
Fetching gem metadata from http://rubygems.org/.......
Fetching gem metadata from http://rubygems.org/..
[IT HANGS HERE FOREVER]
Anyone has a clue?
Fixed by adding bundler to the gem file and forcing a version
gem 'bundler', '1.2.1'
Ok, fixed for good I think.
Turns out it only works when explicitly specifying the last versions of heroku and bundler.
The strange thing is that it can bundle without the explicit versions locally but not when deploying to heroku.
gem 'heroku', '2.33.0'
gem 'bundler', '1.2.1'
For me changing the protocol to fetch gem fixed the problem.
I changed https://github.com/epetre/negative-captcha.git to git://github.com/epetre/negative-captcha.git in gem file. Bundled it and pushed to heroku and it works.