I'm using Capistrano along with the capistrano_rsync_with_remote_cache gem when deploying applications.
The problem occourred after upgrading the deploy server with new software:
capistrano 2.5.10 -> 2.6.0
capistrano_rsync_with_remote_cache 2.3.6 -> 2.4.0
ruby 1.8.6 -> 1.8.7
ruby-gems 1.3.5 -> 1.3.7
the error message:
http://pastebin.com/bD3azxFZ
The top most error:
/var/lib/gems/1.8/gems/capistrano-2.6.0/lib/capistrano/recipes/deploy/scm/base.rb:94:in sync': sync' is not implemented by Capistrano::Deploy::SCM::None (NotImplementedError) from
/var/lib/gems/1.8/gems/capistrano_rsync_with_remote_cache-2.4.0/lib/capistrano/recipes/deploy/strategy/rsync_with_remote_cache.rb:110:in
The line from the file rsync_with_remote_cache.rb:110:
source.sync(revision, local_cache_path)
However this is the same line used in the previous version (2.3.6) of capistrano_rsync_with_remote_cache where the NotImplementedError isn't pressent.
The deploy.rb file used with both versions
http://pastebin.com/EbPkCxyN
what should I change in order to make it deploy again with the newer version?
Sync only works when an SCM is set. You have set :scm, :none in your deploy.rb. Change it accordingly to your SCM. set :scm, :git or the like…
Just had the same error here and got it fixed and thought more people might run into this - and apparently do.
Related
I am trying to install Magento 2.3.5 using composer.
muk#muk:/var/www/html$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.3.5 magento23
Creating a "magento/project-community-edition" project at "./magento23"
Installing magento/project-community-edition (2.3.5-p1)
- Installing magento/project-community-edition (2.3.5-p1): Loading from cache
Created project in /var/www/html/magento23
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 463 installs, 0 updates, 0 removals
- Installing magento/magento-composer-installer (0.1.13): Loading from cache
- Installing laminas/laminas-dependency-plugin (1.0.3): Loading from cache
Plugin installation failed (include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory), rolling back
- Removing laminas/laminas-dependency-plugin (1.0.3)
[ErrorException]
include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory
create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [<package>] [<directory>] [<version>]
I am getting following error.
Plugin installation failed (include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory), rolling back
- Removing laminas/laminas-dependency-plugin (1.0.3)
My Composer version
muk#muk:/var/www/html$ composer --version
Composer version 1.10.5 2020-04-10 11:44:22
I am using VirtualBox with Shared folder.
How can I fix it?
Note: To fix it I stopped using shared folder. Now I keep the entire code in the VM and do not use shared folder. For file synching I am using mutagen.
if anyone runs into this issue, it looks to be a problem with virtualBox and shared folders. when unzipping files, they are not immediately available in the environment.
the solution is by rkamp and is also available here:
https://stackoverflow.com/a/66413857/1470145
in short, one needs to override unzip to add a brief delay after unzipping.
I thought I had the same issue, but turned out it was something else.
The upgrade went OK for me, for a sandbox/clean 2.3.4 install, and a client project running 2.3.4.
A few things:
This could possibly be an issue with your cache, try to clear your composer laminas cache (~/.composer/cache/files/laminas usually)
Although it would complain about that, you've possibly got unmet platform requirements (php version, etc.)
Try clearing your entire composer cache (~/.composer)
Double-check the repository URL (should it be 2.3.5 or 2.3.5-p1?)
Hope that helps
Starting with a brand new project, I am trying to install Eureka through Carthage. I set up a Cartfile with the specified line: github "xmartlabs/Eureka" ~> 3.0.0 as instructed.
I then execute with: carthage update --platform iOS
The build fails with the message:
Task failed with exit code 65" with the further message that the
project likely failed to compile. Checking the log file as instructed
I see the following: "error: SWIFT_VERSION '3.0' is unsupported,
supported versions are: 4.0, 4.2, 5.0. (in target 'Eureka')
I am using Xcode 10.2.1 and the new project defaults Swift Compiler Language to Swift 5. However, this is for the target of the new project. I see in the error the version is 3.0 for target Eureka.
Do I need to change something else for the default running through the terminal? Do I have some old version of a setting from Swift 3.0 hanging around somewhere?
Thank you, version Eureka 5.0 solved it. Unfortunately I was using the command from the webpage https://eurekacommunity.github.io/"github which says use: "xmartlabs/Eureka" ~> 3.0.0"
Only when using cocoapods(after run pod install), generamba setup failes with the following message when settin path to a .xcodeproj.
The path to a .xcodeproj file of the project is 'GrambaSample.xcodeproj'. Do you want to use it? (yes/no) yes
/Library/Ruby/Gems/2.3.0/gems/xcodeproj-1.4.2/lib/xcodeproj/project/object.rb:321:in `configure_with_plist': [!] Xcodeproj doesn't know about the following attributes {"inputFileListPaths"=>[], "outputFileListPaths"=>[]} for the 'PBXShellScriptBuildPhase' isa. (RuntimeError)
This error won't appear is not using cocoapods.
How can I be able to setup Generamba while using cocoapods.
To avoid this issue you should update CocoaPods to the latest beta version by executing
gem install cocoapods --pre
Latest beta version of CocoaPods now using inputFileListPaths and outputFileListPaths.
More info here See .xcfilelist Support
Context
We are trying to use edeliver to deploy a "Hot Upgrade" of a Phoenix Web Application to a remote Virtual Machine instance.
Our aim is to build an "upgrade" version of the app each time so that the app can be "hot" upgraded in production without any down-time.
We have succeeded in doing this "hot upgrade" on a "Hello World" phoenix app:
https://github.com/nelsonic/hello_world_edeliver which is automatically deployed from Travis-CI when the build passes. see: https://travis-ci.org/nelsonic/hello_world_edeliver/builds/259965752#L1752
So, in theory this technique should work for our "real" app.
Attempting to Deploy a "Real" Phoenix App using Edeliver
Ran the following command (to build the upgrade):
mix edeliver build upgrade --auto-version=git-revision --from=$(git rev-parse HEAD~) --to=$(git rev-parse HEAD) --verbose
i.e. "build the upgrade from the previous git revision to the current one"
So far, so good. "Release successfully built!"
Error: vm.args: No such file or directory
When we attempt to deploy the upgrade:
mix edeliver deploy upgrade to production --version=1.0.3+86d55eb --verbose
cat: /home/hladmin/healthlocker/releases/1.0.3+86d55eb/vm.args: No such file or directory
Note: we have a little bash script that reads the latest upgrade version available in .deliver/releases and deploys that see: version.sh
Question:
Is there a way to ignore the absence of the vm.args file and continue the deployment?
Or if the file is required to complete the deployment, is there some documentation on how to create the file?
Note: we have read the distillery "Runtime Configuration" docs: https://github.com/bitwalker/distillery/blob/master/docs/Runtime%20Configuration.md and are sadly none-the-wiser ...
Additional Info
Environment
Localhost: Mac running Elixir 1.4.2
Build Host: Ubuntu 16.04.2 LTS running Elixir 1.4.5
mix.exs file: https://github.com/healthlocker/healthlocker/blob/continuous-delivery/mix.exs
edeliver version: 1.4.4
Build tool: distillery version: 1.4.0
Umbrella project: yes.
This question was also asked on: https://github.com/edeliver/edeliver/issues/234
As mentioned by others, the vm.args file is necessary for BEAM to run the release. A default file is created by distillery during the release build process and should be located in releases/<version>/vm.args. From your log output it looks like expected directory is being checked.
Can you show us the contents of /home/hladmin/healthlocker/releases/?
Can you confirm that the default vm.args file is being created when building the release and extracting it (outside of the upgrade process)?
You also asked:
Or if the file is required to complete the deployment, is there some documentation on how to create the file?
If diagnosing the problem with the default vm.args file doesn't get you anywhere, you can also write your own file and configure distillery to use that file instead of the default. The details for this are in the distillery configuration docs. In short,
add the vm_args setting to your distillery config, which should be at rel/config.exs(relative to your project root), for example:
environment :prod do
set vm_args: "<path>/vm.args"
[...]
end
I updated to Ruby 2.0 and Rails 4.0 and RubyMine stopped working.
If I do my Rails commands through command line tool, they work just fine but if I want to run my project through RubyMine (the latest version) I get error 134 and No Rails Founds in the SDK error.
So I am sure it is not a big deal and it is just some minor setting that needs to be updated in the IDE but can't figure it out yet. And not sure what kind of details do I need to provide so here is Tools -> Show Gem Environment info from the IDE:
RUBYGEMS VERSION: 2.0.3
RUBY VERSION: 2.0.0 (2013-07-05 patchlevel 251) [x86_64-darwin12.4.0]
INSTALLATION DIRECTORY: /Users/Jony/.rvm/gems/ruby-2.0.0-head
RUBY EXECUTABLE: /Users/Jony/.rvm/rubies/ruby-2.0.0-head/bin/ruby
EXECUTABLE DIRECTORY: /Users/Jony/.rvm/gems/ruby-2.0.0-head/bin
RUBYGEMS PLATFORMS:
ruby
x86_64-darwin-12
GEM PATHS:
/Users/Jony/.rvm/gems/ruby-2.0.0-head
/Users/Jony/.rvm/gems/ruby-2.0.0-head#global
GEM CONFIGURATION:
:update_sources => true
:verbose => true
:backtrace => false
:bulk_threshold => 1000
REMOTE SOURCES:
https://rubygems.org/
----------------------
IDE: JetBrains RubyMine 5.4.3.2.1, build #RM-129.861
OS: Mac OS X 10.8.4[x86_64]
Java: 1.6.0_51-b11-456-11M4508
RubyMine SDK Environment:
Sdk: RVM: ruby-2.0.0-head
Sdk Version: ver.2.0.0p251 p251
Ruby Interpreter: /Users/Jony/.rvm/rubies/ruby-2.0.0-head/bin/ruby
RVM Sdk: yes, gemset:[default]
RVM Home: /Users/Jony/.rvm
Sdk Language Level: 1.9
Sdk Load Path:
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/site_ruby/2.0.0
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/site_ruby/2.0.0/x86_64-darwin12.4.0
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/site_ruby
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/vendor_ruby/2.0.0
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin12.4.0
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/vendor_ruby
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/2.0.0
~/.rvm/rubies/ruby-2.0.0-head/lib/ruby/2.0.0/x86_64-darwin12.4.0
/Applications/RubyMine.app/rubystubs20
Sdk Gem paths:
~/.rvm/gems/ruby-2.0.0-head/bundler/gems
~/.rvm/gems/ruby-2.0.0-head/gems
~/.rvm/gems/ruby-2.0.0-head#global/gems
Gems used for 'untitled4':
sprockets-rails (2.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/sprockets-rails-2.0.0
activerecord (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/activerecord-4.0.0
rack-test (0.6.2)
~/.rvm/gems/ruby-2.0.0-head/gems/rack-test-0.6.2
activesupport (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/activesupport-4.0.0
coffee-script-source (1.6.3)
~/.rvm/gems/ruby-2.0.0-head/gems/coffee-script-source-1.6.3
turbolinks (1.2.0)
~/.rvm/gems/ruby-2.0.0-head/gems/turbolinks-1.2.0
bundler (1.3.5)
~/.rvm/gems/ruby-2.0.0-head#global/gems/bundler-1.3.5
activemodel (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/activemodel-4.0.0
mail (2.5.4)
~/.rvm/gems/ruby-2.0.0-head/gems/mail-2.5.4
rack (1.5.2)
~/.rvm/gems/ruby-2.0.0-head/gems/rack-1.5.2
json (1.8.0)
~/.rvm/gems/ruby-2.0.0-head/gems/json-1.8.0
minitest (4.7.5)
~/.rvm/gems/ruby-2.0.0-head/gems/minitest-4.7.5
tzinfo (0.3.37)
~/.rvm/gems/ruby-2.0.0-head/gems/tzinfo-0.3.37
sass-rails (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/sass-rails-4.0.0
actionmailer (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/actionmailer-4.0.0
hike (1.2.3)
~/.rvm/gems/ruby-2.0.0-head/gems/hike-1.2.3
coffee-script (2.2.0)
~/.rvm/gems/ruby-2.0.0-head/gems/coffee-script-2.2.0
activerecord-deprecated_finders (1.0.3)
~/.rvm/gems/ruby-2.0.0-head/gems/activerecord-deprecated_finders-1.0.3
thread_safe (0.1.0)
~/.rvm/gems/ruby-2.0.0-head/gems/thread_safe-0.1.0
sqlite3 (1.3.7)
~/.rvm/gems/ruby-2.0.0-head/gems/sqlite3-1.3.7
sdoc (0.3.20)
~/.rvm/gems/ruby-2.0.0-head/gems/sdoc-0.3.20
actionpack (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/actionpack-4.0.0
tilt (1.4.1)
~/.rvm/gems/ruby-2.0.0-head/gems/tilt-1.4.1
jquery-rails (3.0.2)
~/.rvm/gems/ruby-2.0.0-head/gems/jquery-rails-3.0.2
mime-types (1.23)
~/.rvm/gems/ruby-2.0.0-head/gems/mime-types-1.23
railties (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/railties-4.0.0
sprockets (2.10.0)
~/.rvm/gems/ruby-2.0.0-head/gems/sprockets-2.10.0
arel (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/arel-4.0.0
polyglot (0.3.3)
~/.rvm/gems/ruby-2.0.0-head/gems/polyglot-0.3.3
thor (0.18.1)
~/.rvm/gems/ruby-2.0.0-head/gems/thor-0.18.1
rdoc (3.12.2)
~/.rvm/gems/ruby-2.0.0-head/gems/rdoc-3.12.2
rake (10.1.0)
~/.rvm/gems/ruby-2.0.0-head#global/gems/rake-10.1.0
coffee-rails (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/coffee-rails-4.0.0
i18n (0.6.4)
~/.rvm/gems/ruby-2.0.0-head/gems/i18n-0.6.4
multi_json (1.7.7)
~/.rvm/gems/ruby-2.0.0-head/gems/multi_json-1.7.7
sass (3.2.9)
~/.rvm/gems/ruby-2.0.0-head/gems/sass-3.2.9
rails (4.0.0)
~/.rvm/gems/ruby-2.0.0-head/gems/rails-4.0.0
execjs (1.4.0)
~/.rvm/gems/ruby-2.0.0-head/gems/execjs-1.4.0
treetop (1.4.14)
~/.rvm/gems/ruby-2.0.0-head/gems/treetop-1.4.14
atomic (1.1.10)
~/.rvm/gems/ruby-2.0.0-head/gems/atomic-1.1.10
erubis (2.7.0)
~/.rvm/gems/ruby-2.0.0-head/gems/erubis-2.7.0
uglifier (2.1.1)
~/.rvm/gems/ruby-2.0.0-head/gems/uglifier-2.1.1
jbuilder (1.4.2)
~/.rvm/gems/ruby-2.0.0-head/gems/jbuilder-1.4.2
builder (3.1.4)
~/.rvm/gems/ruby-2.0.0-head/gems/builder-3.1.4
And also a screen shot of my SDK settings just in case:
I solved this issue of No Rails SDK found by following.
Step 1.
Figure out Ruby version and bundle version of your project.
Step 2.
Add correct Ruby SDK and GEMs from preferences in Rubymine.
Preferences > Languages & Framework > Ruby SDK and Gems > [Select your RVM version] > [Select correct gem version of bundle] > Apply
I solved this problem by deleting the project from RubyMine's history (close project and then hit the x for the project on the left side) and deleting the .idea directory of my project. After I opened the project in RubyMine again, it worked.
I solved this by installed another Ruby version ,and it installed in Global file
/user/share/rvm/rubies/ruby-2.5.1
The first time I installed the latest Ruby version in my local rvm file, all gem files didn't add in Rubymine which only contains some base ruby files.
~/.rvm/rubies/ruby-2.6.3
I don't know why is that,but I don't think I need to know the reason, at least now.
If the answer by #atul_vaibhai doesn't work.
Close any open terminals and your project and open your project
Uninstall any new versions of ruby than the one that your application requires.
rvm remove <other versions>
If this solves your problem, then you need to figure out how to parallely keep another version without affecting any other application. You must be doing something wrong in configuring the application.
Had the same error message without updating anything.
Invalidating the Cache / Restart worked for me.