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>
Related
I am getting this are after running all of my test cases in the cypress dashboard. Can anyone help me to solve this issue? Test cases are running no issues in there.
An error was thrown in your plugins file while executing the handler for the after:run event.
The error we received was:
Error: spawn cucumber-json-formatter.exe ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
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 ?
I am running a javascript app in heroku (scoold) and have been told by the developer that there is a new jar file to upload. I Downloaded the heroku cli and jar file and ran the following commands as instructed:
heroku plugins:install java
heroku deploy:jar scoold-x.y.z.jar --app myscooldapp
However, I am getting the following error:
C:\Sites>heroku deploy:jar scoold-pro-1.37.1.jar --app nocodeflow
Uploading scoold-pro-1.37.1.jar
events.js:187
throw er; // Unhandled 'error' event
^
Error: spawn java ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn java',
path: 'java',
spawnargs: [
'-Dheroku.appName=nocodeflow',
'-Xmx1g',
'-Dheroku.jarFile=scoold-pro-1.37.1.jar',
'-Dheroku.jarOpts=',
'-cp',
'C:\\Users\\Artwe\\AppData\\Local\\heroku\\node_modules\\#heroku-cli\\plugin-java\\lib\\heroku-deploy-complete.jar',
'com.heroku.sdk.deploy.DeployJar'
]
}
I create a ticket on the Heroku support center, because I had the same problem.
I want to deploy a simple war and normally I don't need any Node.js ...
I am trying to deploy executable war (java -jar myapp.jar) on Heroku, which I am successfully able to execute on local machine.
I followed below steps to do it on heroku using CLI
heroku plugins:install java
heroku create --no-remote --app testjar
heroku deploy:jar target/my-app.jar --app testjar
First two steps run fine... but in 3rd I got below exception. Any idea on the cause ? Or what information it wants? I Have given it all as per the document https://devcenter.heroku.com/articles/deploying-executable-jar-files
Uploading funApp.jar
events.js:167
throw er; // Unhandled 'error' event
^
Error: spawn java ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:19)
at onErrorNT (internal/child_process.js:421:16)
at process.internalTickCallback (internal/process/next_tick.js:72:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:252:12)
at onErrorNT (internal/child_process.js:421:16)
at process.internalTickCallback (internal/process/next_tick.js:72:19)
docker#default:/c/Users/Abhi/DockerAppHub/heroku/bin$ ./heroku deploy:jar ./funApp.jar --app testjar08
Uploading funApp.jar events.js:167
throw er; // Unhandled 'error' event
^
Error: spawn java ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:19)
at onErrorNT (internal/child_process.js:421:16)
at process.internalTickCallback (internal/process/next_tick.js:72:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:252:12)
at onErrorNT (internal/child_process.js:421:16)
at process.internalTickCallback (internal/process/next_tick.js:72:19)
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.