I just installed the latest docpad. Installed sass plugin, and I've been getting this error when I used the 'run' command. I'm pretty novice with node and docpad so I'm not really sure whats going on. Anybody have this problem lately?
info: Welcome to DocPad v6.64.2 (local installation: /Users/zachfrank/Desktop/mm-t/node_modules/docpad)
info: Contribute: http://docpad.org/docs/contribute
info: Plugins: eco, livereload, sass
info: Environment: development
info: DocPad listening to http://0.0.0.0:9778/ on directory /Users/zachfrank/Desktop/mm-t/out
info: LiveReload listening to new socket on channel /docpad-livereload
info: Generating...
warning: Something went wrong while rendering: styles/app.css.scss
exited with a non-zero status code
error: Something went wrong with the action
error: An error occured:
Error: exited with a non-zero status code
at ChildProcess.<anonymous> (/Users/zachfrank/Desktop/mm-t/node_modules/docpad-plugin- sass/node_modules/safeps/out/lib/safeps.js:165:23)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Socket.<anonymous> (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)
info: Shutting down... cya next time!
Here's my 'gem list' if maybe I have a conflicting version of sass or something..
*** LOCAL GEMS ***
bourbon (4.0.0)
bundler (1.6.2)
chunky_png (1.3.0)
compass (0.12.6)
foundation (1.0.4)
fssm (0.2.10)
neat (1.6.0)
sass (3.3.5, 3.2.19)
thor (0.19.1)
Any help greatly appreciated!
Related
I realized that because I was using expo go to create my react native project I was unable to link firebase to it, so I decided I would use the CLI in hopes that I could follow a tutorial online that I found that uses it. Long story short spent 4 hours fiddling with ruby, homebrew, watchman, node, etc. And I have nearly got it to download the React native CLI, however I am getting this error. I originally was getting an error that said the Gem needed 2.7.5 and I was using 3.0.0 so I switched it using rvm and now this is the error I get. TBH if someone knows how to connect firebase to react-native using expo go I would rather just keep working on that project than starting a new one, but I don't think it is possible, so if someone can help me figure out why I am getting this error that would be helpful as well.
here is the full error:
Installing dependencies
✔ CocoaPods (https://cocoapods.org/) is not installed. CocoaPods is necessary for the iOS project to run correctly. Do you want to install it? › Yes, with gem (may require sudo)
✔ Installing CocoaPods
✖ Installing Bundler
error Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory: /Users/jonnywerthman/Desktop/Dev
stuff/personal/90dayz/Dayz90/vendor/bundle/ruby/2.7.0/gems/ffi-1.15.5/ext/ffi_c
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/bin/ruby -I
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0 -r
./siteconf20221226-91293-hikzkd.rb extconf.rb
checking for ffi_prep_closure_loc() in -lffi... no
checking for ffi_prep_closure_loc() in -llibffi... no
checking for ffi_prep_closure_loc() in -llibffi-8... no
checking for whether -Wl,--exclude-libs,ALL is accepted as LDFLAGS... no
checking for whether -pthread is accepted as LDFLAGS... yes
creating extconf.h
creating Makefile
current directory: /Users/jonnywerthman/Desktop/Dev
stuff/personal/90dayz/Dayz90/vendor/bundle/ruby/2.7.0/gems/ffi-1.15.5/ext/ffi_c
make "DESTDIR=" clean
current directory: /Users/jonnywerthman/Desktop/Dev
stuff/personal/90dayz/Dayz90/vendor/bundle/ruby/2.7.0/gems/ffi-1.15.5/ext/ffi_c
make "DESTDIR="
/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
/bin/sh: -c: line 1: syntax error: unexpected end of file
make: *** ["/Users/jonnywerthman/Desktop/Dev] Error 2
make failed, exit code 2
Gem files will remain installed in /Users/jonnywerthman/Desktop/Dev
stuff/personal/90dayz/Dayz90/vendor/bundle/ruby/2.7.0/gems/ffi-1.15.5 for
inspection.
Results logged to /Users/jonnywerthman/Desktop/Dev
stuff/personal/90dayz/Dayz90/vendor/bundle/ruby/2.7.0/extensions/x86_64-darwin-22/2.7.0/ffi-1.15.5/gem_make.out
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:99:in
`run'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:51:in
`block in make'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:43:in
`each'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:43:in
`make'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/ext_conf_builder.rb:63:in
`block in build'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/tempfile.rb:291:in
`open'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/ext_conf_builder.rb:30:in
`build'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:169:in
`block in build_extension'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:165:in
`synchronize'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:165:in
`build_extension'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:210:in
`block in build_extensions'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:207:in
`each'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/ext/builder.rb:207:in
`build_extensions'
/Users/jonnywerthman/.rvm/rubies/ruby-2.7.5/lib/ruby/2.7.0/rubygems/installer.rb:844:in
`build_extensions'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/rubygems_gem_installer.rb:72:in
`build_extensions'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/rubygems_gem_installer.rb:28:in
`install'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/source/rubygems.rb:200:in
`install'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/installer/gem_installer.rb:54:in
`install'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/installer/gem_installer.rb:16:in
`install_from_spec'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/installer/parallel_installer.rb:155:in
`do_install'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/installer/parallel_installer.rb:146:in
`block in worker_pool'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/worker.rb:62:in
`apply_func'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/worker.rb:57:in
`block in process_queue'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/worker.rb:54:in
`loop'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/worker.rb:54:in
`process_queue'
/Users/jonnywerthman/.rvm/gems/ruby-2.7.5/gems/bundler-2.4.1/lib/bundler/worker.rb:90:in
`block (2 levels) in create_threads'
An error occurred while installing ffi (1.15.5), and Bundler cannot continue.
In Gemfile:
cocoapods was resolved to 1.11.3, which depends on
cocoapods-core was resolved to 1.11.3, which depends on
typhoeus was resolved to 1.4.0, which depends on
ethon was resolved to 0.16.0, which depends on
ffi
✖ Installing Bundler
error Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS.
Error: Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS.
at createFromTemplate (/Users/jonnywerthman/node_modules/#react-native-community/cli/build/commands/init/init.js:169:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.initialize [as func] (/Users/jonnywerthman/node_modules/#react-native-community/cli/build/commands/init/init.js:222:3)
at async Command.handleAction (/Users/jonnywerthman/node_modules/#react-native-community/cli/build/index.js:140:9)
I tried a lot of different stuff, but I am nearing my breaking point with this. pls help.
Look at the error:
/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
/bin/sh: -c: line 1: syntax error: unexpected end of file
make: *** ["/Users/jonnywerthman/Desktop/Dev] Error 2
This means "The string "/Users/jonnywerthman/Desktop/Dev doesn't have an end set of quotation marks and I was expecting to find one." And ultimately that means it can't continue executing.
I don't know and can't speak to why the path isn't being properly quoted. It's probably a misconfiguration of the tools that are being run.
The fastest and simplest solution is to remove the whitespace from the path, so that you turn this:
/Users/jonnywerthman/Desktop/Dev stuff/
Into this:
/Users/jonnywerthman/Desktop/Devstuff/
Then retry the operation.
I want to apply this theme, but there is an error while building it.
It works in local, but it doesn't build.
https://github.com/rubygems/bundler/issues/4375
I saw it through this link, but I don't know how to match it because the server also says that using a fixed version of the bundler is the solution.
Error: The process '/opt/hostedtoolcache/Ruby/3.1.2/x64/bin/bundle' failed with exit code 16
at ExecState._setResult (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:6023:25)
at ExecState.CheckComplete (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:6006:18)
at ChildProcess.<anonymous> (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:5900:27)
at ChildProcess.emit (node:events:390:28)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
$ which jekyll
>>> /Users/GyeongminKim/.rbenv/shims/jekyll
$ which gem
>>> /Users/GyeongminKim/.rubies/ruby-3.1.2/bin/gem
$ which bundle
>>> /Users/GyeongminKim/.rubies/ruby-3.1.2/bin/bundle
$ bundle version
>>> Bundler version 2.3.7 (2022-09-15 commit unknown)
$ ruby --version
>>> ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21]
I was getting the same error. This command helped me to resolve my issue:
bundle lock --add-platform x86_64-linux
source
I'm getting a weird error while trying to jekyll serve.
Dependency Error: Yikes! It looks like you don't have jemoji or one of
its dependencies installed. In order to use Jekyll as currently configured,
you'll need to install this gem. The full error message from Ruby is: 'Unable
to activate activesupport-4.2.7.1, because json-2.0.3 conflicts with
json (>= 1.7.7, ~> 1.7)' If you run into trouble, you can find helpful resources
at https://jekyllrb.com/help/!
I've uninstalled and reinstalled but can't figure the problem out. I've done a gem update and the actual versions I have are below:
*** LOCAL GEMS ***
activesupport (5.0.1, 4.2.7.1)
...
jemoji (0.8.0)
json (2.0.3, default: 2.0.2, 1.8.6)
...
When running a compass task with Gulp (on OSX), I receive the following error. I've tried installing specific versions of both compass and sass (in various orders) without any notable effect.
[17:25:46] LoadError on line ["54"] of /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb: cannot load such file -- compass/import-once/activate
Run with --trace to see the full backtrace
events.js:72
throw er; // Unhandled 'error' event
^
Error: Compass failed
at Transform.<anonymous> (/Users/liamegan/Projects/WTC/nintendo.wethecollective.com/html/Websites/Kids/web/node_modules/gulp-compass/index.js:37:28)
at ChildProcess.<anonymous> (/Users/liamegan/Projects/WTC/nintendo.wethecollective.com/html/Websites/Kids/web/node_modules/gulp-compass/lib/compass.js:136:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Socket.<anonymous> (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)
My compass version is 0.12.7 and my sass version is 3.3.13 however I've also tried with sass 3.2.19.
My sass gulp process is as follows:
gulp.task('sass', function() {
gulp
.src('./_src/sass/screen.scss')
.pipe(compass({
config_file: './config.rb'
}))
.pipe(gulp.dest('./assets/css'))
})
Any help or insight would be greatly appreciated.
Cheers,
L
I fixed this with the following:
sudo gem uninstall sass
sudo gem uninstall compass
sudo gem install sass
sudo gem install compass --pre
This installed the prerelease version of compass which works with the latest, stable version of sass.
Just updated to vagrant 1.6.2
Ran vagrant up and got the following error
Vagrant failed to initialize at a very early stage:
The plugins failed to load properly. The error message given is shown below.
undefined method `[]' for nil:NilClass
I ran vagrant up --debug and saw the following error message
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::PluginLoadError: The plugins failed to load properly. The error message given is shown below.
undefined method `[]' for nil:NilClass>
ERROR vagrant: The plugins failed to load properly. The error message given is shown below.
undefined method `[]' for nil:NilClass
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.2/lib/vagrant.rb:265:in `rescue in <top (required)>'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.2/lib/vagrant.rb:261:in `<top (required)>'
/Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.2/bin/vagrant:101:in `require'
/Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.2/bin/vagrant:101:in `<main>'
Vagrant failed to initialize at a very early stage:
The plugins failed to load properly. The error message given is shown below.
undefined method `[]' for nil:NilClass
I then tried
vagrant plugin update
This produced the following complaint
Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is:
An error occurred while installing nokogiri (1.6.2.1), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.6.2.1'` succeeds before bundling.
So I ran
gem install nokogiri -v '1.6.2.1'
And this succeeded.
But it didn't solve the problem...
When I now run
vagrant plugin update
I still get the same error I got before installing nokogiri.
Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is:
An error occurred while installing nokogiri (1.6.2.1), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.6.2.1'` succeeds before bundling.
Anyone have a solution for this?
This is a Vagrant issue and is being tracked in https://github.com/mitchellh/vagrant/issues/3769.
Ok. I solved the problem for me at least.
I uninstalled vagrant 1.6.2 and installed vagrant 1.6.1