Running Capistrano. Worked yesterday, not working today. Here's the main error. It's with Gulp... Ran gulp -v and both local and global are 3.9.0
INFO[17d08d58] Running /usr/bin/env gulp --production --no-color on localhost
cap aborted!
SSHKit::Command::Failed: gulp exit status: 256
gulp stdout: [10:25:28] Using gulpfile ...gulpfile.js
[10:25:28] Starting 'clean'...
[10:25:28] Finished 'clean' after 14 ms
[10:25:28] Starting 'default'...
[10:25:28] Starting 'wiredep'...
[10:25:28] Starting 'scssLint'...
[10:25:28] Finished 'scssLint' after 13 μs
[10:25:28] Starting 'jshint'...
[10:25:29] Starting 'browserify'...
[10:25:29] Starting 'fonts'...
[10:25:29] Starting 'images'...
[10:25:29] Finished 'default' after 1.08 s
[10:25:30] Finished 'wiredep' after 1.34 s
[10:25:30] Starting 'styles'...
gulp stderr: stream.js:94
throw er; // Unhandled stream error in pipe.
^
Error: invalid top-level expression
Any help would be greatly appreciated. I also ran capistrano-ssh-doctor and everything was working great.
FOUND IT! It was within the SASS code - there was an error and thus it did not compile properly.
Related
I am setting up opensearch dashboard in my windows PC and following below guide -
https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/DEVELOPER_GUIDE.md
While bootstrapping, I am getting below error -
PS D:\opensearch\OpenSearch-Dashboards> yarn osd bootstrap
yarn run v1.22.18
$ node scripts/osd bootstrap
info [opensearch-dashboards] running yarn
$ node ./preinstall_check
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "typescript#4.0.2" is incompatible with requested version "typescript#~4.5.2"
success Already up-to-date.
succ yarn.lock analysis completed without any issues
succ 10 bootstrap builds are cached
info [#osd/i18n] running [osd:bootstrap] script
info [#osd/monaco] running [osd:bootstrap] script
info [#osd/opensearch-archiver] running [osd:bootstrap] script
info [#osd/opensearch] running [osd:bootstrap] script
ERROR [bootstrap] failed:
ERROR Error: Command failed with exit code 1: C:\Users\st\AppData\Roaming\nvm\v14.18.2\node_modules\yarn\bin\yarn.js run osd:bootstrap
'rm' is not recognized as an internal or external command,
operable program or batch file.
error Command failed with exit code 1.
$ rm -rf target && tsc
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
at makeError (D:\opensearch\OpenSearch-Dashboards\packages\osd-pm\dist\index.js:25150:11)
at handlePromise (D:\opensearch\OpenSearch-Dashboards\packages\osd-pm\dist\index.js:24085:26)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async D:\opensearch\OpenSearch-Dashboards\packages\osd-pm\dist\index.js:9051:9
at async scheduleItem (D:\opensearch\OpenSearch-Dashboards\packages\osd-pm\dist\index.js:10938:9)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
what I see here is, rm command is not recognized in windows and which is correct.
So how to fix this ?
Yarn Install successful:
C:\Users\Yael\Downloads\metamask-extension-8.0.9\metamask-extension-8.0.9>yarn
yarn install v1.22.10
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 2.77s.
Yarn dist error:
C:\Users\Yael\Downloads\metamask-extension-8.0.9\metamask-extension-8.0.9>yarn dist
yarn run v1.22.10
$ yarn build prod
$ node development/build/index.js prod
running task "prod"...
Starting 'prod'...
Starting 'clean'...
(node:12548) ExperimentalWarning: The fs.promises API is experimental
Finished 'clean'
Starting 'styles:prod'...
Finished 'styles:prod'
Starting 'scripts:deps:background'...
Starting 'scripts:deps:ui'...
Starting 'scripts:core:prod:background'...
Starting 'scripts:core:prod:ui'...
Starting 'scripts:core:prod:phishing-detect'...
Starting 'scripts:core:prod:contentscript'...
Starting 'static:prod'...
Starting 'manifest:prod'...
events.js:174
throw er; // Unhandled 'error' event
^
Error: spawn yarn ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
C:\Users\Yael\Downloads\metamask-extension-8.0.9\metamask-extension-8.0.9>
I'm trying to set up a basic workflow with Gulp and I'm getting the following error whenever I call gulp-notify.
Design5-Joel:Sura-child design5$ gulp notify
[14:00:17] Using gulpfile ~/Documents/Websites/atoll-wp/wp-content/themes/Sura-child/gulpfile.js
[14:00:17] Starting 'notify'...
[14:00:17] Finished 'notify' after 10 ms
[14:00:17] gulp-notify: [Gulp notification] Hello Gulp!
[14:00:47] gulp-notify: [Error in notifier] Error in plugin 'gulp-notify'
Message:
Command failed: /Users/design5/Documents/Websites/atoll-wp/wp-content/themes/Sura-child/node_modules/node-notifier/vendor/terminal-notifier.app/Contents/MacOS/terminal-notifier -title "Gulp notification" -message "Hello Gulp!" -appIcon "/Users/design5/Documents/Websites/atoll-wp/wp-content/themes/Sura-child/node_modules/gulp-notify/assets/gulp.png" -json "true"
Details:
killed: true
code: null
signal: SIGTERM
cmd: /Users/design5/Documents/Websites/atoll-wp/wp-content/themes/Sura-child/node_modules/node-notifier/vendor/terminal-notifier.app/Contents/MacOS/terminal-notifier -title "Gulp notification" -message "Hello Gulp!" -appIcon "/Users/design5/Documents/Websites/atoll-wp/wp-content/themes/Sura-child/node_modules/gulp-notify/assets/gulp.png" -json "true"
The strange thing is that everything in the function fires, including the notification, and then exactly 30 seconds later the error comes up. This is particularly a problem if I want to watch a folder.
If anyone else has found a solution to this it would be much appreciated
edit: gulp-notify isn't a mandatory aspect of the function, so the easy solution would be to just disable notify but I'd like to be able to solve this in case I run into similar issues in the future.
I've tried;
updating all dependencies
verifying node's cache
reinstalling all packages
running package.json and gulpfile.js through validators.
Does anyone have a clue or any direction how to fix this error.
Running CentOS 6.7
[07:42 PM]-[vagrant#machine1]-[/var/www/laracast]
$ gulp
[19:42:52] Using gulpfile /var/www/laracast/gulpfile.js
[19:42:52] Starting 'default'...
[19:42:52] Starting 'sass'...
Fetching Sass Source Files...
- resources/assets/sass/app.scss
Saving To...
- public/css/app.css
[19:42:53] Finished 'default' after 733 ms
[19:42:53] gulp-notify: [Laravel Elixir] Sass Compiled!
[19:42:53] Finished 'sass' after 833 ms
[19:42:53] gulp-notify: [Error in notifier] Error in plugin 'gulp-notify'
Message:
(notify-send:24561): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Disable gulp notify by export DISABLE_NOTIFIER=true
If you are running on a system that handles notifications poorly or you simply do not wish to use gulp-notify but your project does? You can disable gulp-notify by using enviroment variable DISABLE_NOTIFIER.
export DISABLE_NOTIFIER=true;
This will disable all methods; notify(), notify.onError and notify.withReporter.
See details here: disable-gulp-notify
Everytime I run gulp, I get no warning messages in the console, only when I re-vist my Laravel application:
File js/vendor.js not defined in asset manifest. (View:
/Users/Documents/app/resources/views/layouts/app.blade.php) (View:
/Users/Documents/app/resources/views/layouts/app.blade.php)
My gulpfile.js setup is:
var elixir = require('laravel-elixir');
elixir(function(mix) {
mix.scripts([
'../bower/jquery/dist/jquery.js',
'../bower/bootstrap/dist/js/bootstrap.js'
], 'public/js/vendor.js')
.version(["js/vendor.js", "build/vendor"]);
mix.scripts([
'../bower/holderjs/holder.js',
'../bower/bootstrap-select/dist/js/bootstrap-select.js',
'../bower/jasny-bootstrap/dist/js/jasny-bootstrap.js'
], 'public/js/addConsultant.js')
.version(["js/addConsultant.js", "build/addConsultant"]);
});
The output from running the gulp command is:
[16:12:44] Using gulpfile ~/Documents/compare/gulpfile.js [16:12:44]
Starting 'default'... [16:12:44] Starting 'scripts'...
Fetching Scripts Source Files...
- resources/assets/bower/jquery/dist/jquery.js
- resources/assets/bower/bootstrap/dist/js/bootstrap.js
Saving To...
- public/js/vendor.js
[16:12:45] Finished 'default' after 844 ms [16:12:45] gulp-notify:
[Laravel Elixir] Scripts Merged! [16:12:45] Finished 'scripts' after
1.02 s [16:12:45] Starting 'version'...
Fetching Version Source Files...
- public/js/vendor.js
- public/build/vendor/**/*
Saving To...
- public/build
[16:12:45] Finished 'version' after 51 ms [16:12:45] Starting
'scripts'...
Fetching Scripts Source Files...
- resources/assets/bower/holderjs/holder.js
- resources/assets/bower/bootstrap-select/dist/js/bootstrap-select.js
- resources/assets/bower/jasny-bootstrap/dist/js/jasny-bootstrap.js
Saving To...
- public/js/addConsultant.js
[16:12:46] gulp-notify: [Laravel Elixir] Scripts Merged! [16:12:46]
Finished 'scripts' after 201 ms [16:12:46] Starting 'version'...
Fetching Version Source Files...
- public/js/addConsultant.js
- public/build/addConsultant/**/*
Saving To...
- public/build
[16:12:46] Finished 'version' after 55 ms
Inside the public/build/rev-manifest.json file is the following:
{ "js/addConsultant.js": "js/addConsultant-4f9f7941f8.js" }
Why am I getting this error? Any help would be hugely appreciated.