When I use the command d:\path>docpad run, I have only one choice with Skeleton because I get an error when DocPad tried to updating exchange.
The output of this command:
D:\path>docpad run
info: Welcome to DocPad v6.69.1 (global installation: C:\Users\v20100v\AppData\Roaming\npm\node_modules\docpad)
notice: If everyone who saw this message donated $1/week, maintaining DocPad would become sustainable: http://docpad.org/donate
info: Contribute: http://docpad.org/docs/contribute
info: Plugins:
info: Environment: development
info: Updating the exchange...
This can take a moment...
notice: An error occured fetching the exchange data, this is okay, but not all skeletons will be available to you undefined { code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
info: You are about to create your new project inside your current directory. Below is a list of skeletons to bootstrap
your new project:
1. No Skeleton
Prefer to start from scratch? You can get started without any skeleton if you wish
Which skeleton will you use? [1-1]
1. No Skeleton
>
Information about my configuration :
-> Windows 7
-> node v0.10.13
-> npm v1.3.2
-> docpad v6.69.1
May be a proxy problem, but node and npm work fine with my configuration proxy.
Any idea how to fix this?
Related
Im building a static page in nuxtjs. I added the module nuxt/image and set it up according to the instructions in the documentation. (static with self hosted images)
ssr:true,
target: 'statics",
buildModules: [
// https://go.nuxtjs.dev/vuetify
'#nuxtjs/vuetify',
//https://image.nuxtjs.org
'#nuxt/image'
],
<nuxt-link :to="localePath('/')">
<nuxt-img
id="header-logo"
format="webp"
src="/logos/logo.png">
</nuxt-img>
</nuxt-link>
When i run npm run dev the project compiles but then the development server exists without any errors.
When I deploy it to the server through github actions the action breaks and exits on nuxt generate with the exit code: /home/githubaction/actions-runner/workspace/_temp/eb47b4c6-6c0d-42cc-[9](https://github.com/xxxxxx/xxxxx/runs/6722739489?check_suite_focus=true#step:9:10)019-dca85b061dda.sh: line 1: 17085 Segmentation fault npm run generate Error: Process completed with exit code 139.
Any idea why is that?
Update
I downgraded from version 0.6.2 to 0.6.0 and this seems to resolve the issue.
I am trying to run the collection-examples-as near example but when I run yarn deploy it gives me the following error
$ near dev-deploy --wasmFile="./contract.wasm"
Starting deployment. Account id: dev-1637744501224-6323200, node:
https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file:
./contract.wasm
An error occurred
Error: ENOENT: no such file or directory, open './contract.wasm'
[Error: ENOENT: no such file or directory, open './contract.wasm'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './contract.wasm'
}
error Command failed with exit code 1.
I think the error is it can't find the path to ./contract.wasm so I run yarn build the I tried to deploy it again using yarn deploy but I got another error which is:
$ near dev-deploy --wasmFile="./contract.wasm"
Starting deployment. Account id: dev-1637744501224-6323200, node:
https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file:
./contract.wasm
An error occurred
Error: Can not sign transactions for account dev-1637744501224-6323200 on network
default, no matching key pair found in
InMemorySigner(MergeKeyStore(UnencryptedFileSystemKeyStore(/home/rasha/.near-
credentials), UnencryptedFileSystemKeyStore(/home/rasha/collection-examples-
as/neardev))).
{
type: 'KeyNotFound',
context: undefined
}
any help or suggestions?
There's an issue with old versions of near-cli and dev-deploy.
As a workaround, you can try running the latest cli directly from your terminal:
near dev-deploy --wasmFile="./contract.wasm" -f
Just check that you installed the latest version of near-cli, currently 2.2.0. You can check your version with near --version.
Be sure to run yarn build first, so you'll have the compiled contract.wasm file.
Note: When you run yarn deploy, it uses the old near-cli version defined in package.json. (probably some old version like 1.6.0)
You might also want to check this GitHub issue (dev-deploy error): https://github.com/near/create-near-app/issues/1408
I am running Apache Ignite 2.4.0 and configured Ignite web console using following steps Ignite webconsole build and deploy
same has been configured for production mode in Apache server and after successfully starting Backend, when i access web console from front end I am getting below signup error on Backend Node application console. I have tried multiple configurations but none of them seems to work.
Error: Not Found: /signup
at app.use (/recon/Ignite/web-console/backend/app/apiServer.js:64:33)
at Layer.handle [as handle_request] (/recon/Ignite/web-console/backend/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:317:13)
at /recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:335:12)
at next (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:275:10)
at SessionStrategy.strategy.pass (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/authenticate.js:325:9)
at SessionStrategy.authenticate (/recon/Ignite/web-console/backend/node_modules/passport/lib/strategies/session.js:71:10)
at attempt (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/authenticate.js:348:16)
at authenticate (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/authenticate.js:349:7)
at Layer.handle [as handle_request] (/recon/Ignite/web-console/backend/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:317:13)
at /recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:335:12)
at next (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:275:10)
at initialize (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/initialize.js:53:5)
at Layer.handle [as handle_request] (/recon/Ignite/web-console/backend/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:317:13)
at /recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:335:12)
at next (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:275:10)
Snady, ignite-2.5.0 is on vote now and may be released in several days. I think it make sense to use this version.
Requirements: NodeJS 8.x & MongoDB 3.4.x. // Make sure you have this.
So, I downloaded sources and do the following:
In first terminal:
cd {apache-ignite-2.5.0}/modules/web-console/backend
npm install --no-optional
npm start
In second terminal:
cd {apache-ignite-2.5.0}/modules/web-console/frontend
npm install --no-optional
npm start
In browser do: http://localhost:9000/
EDIT:
Will Ignite Web Console in Docker works for your case?
See: https://hub.docker.com/r/apacheignite/web-console-standalone/
When trying to follow the instructions (https://fabric-composer.github.io/tasks/genapp.html) to generate an Angular app based on a running business network I'm getting a No bower.json present error, using the defaultProfile. It seems to generate a node_modules directory but it's empty, however no angular-app directory is created. I was able to get the app generated by pointing at an existing BNA file as outlined in step 2 of the document but wasn't ideal. Any idea of what mind be going on?
jdockter#ubuntu:~$ yo fabric-composer:angular
WARNING: No configurations found in configuration directory:/home/jdockter/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
Welcome to the Angular2 skeleton app generator
? Do you want to connect to a running Business Network? Yes
? What is the name of the application you wish to generate?: angular-app
? Description of the application: Skeleton Fabric Composer Angular2 project
? Author name: Jon Dockter
? Author email: jdockter#us.ibm.com
? What is the Business Network Identifier?: labor-network-model
? What is the Connection Profile to use? defaultProfile
? Enrollment id: WebAppAdmin
? Enrollment Secret: DJY27pEnl16d
Configuring: angular-app
About to connect to a running business network
I'm all done. Running npm install && bower install for you to install the required dependencies. If this fails, try running the command yourself.
npm WARN enoent ENOENT: no such file or directory, open '/home/jdockter/package.json'
npm WARN jdockter No description
npm WARN jdockter No repository field.
npm WARN jdockter No README data
npm WARN jdockter No license field.
bower ENOENT No bower.json present
Complete
I created this defect to track this:
https://github.com/fabric-composer/fabric-composer/issues/206
Will update here as soon as we know more.
Thanks for the report.
I have a donejs application and its running ok in development mode donejs develop, but when I run it in production mode:
donejs build
donejs deploy (to firebase)
NODE_ENV=production donejs start
it will not start and show an error (see CODE A)
This file: file:my-app/dist/bundles/my-app/index.js:704 corresponds to JQuery 3.x and its not a dependency of the project itself but a dependency of can-connect-feathers (https://github.com/canjs/can-connect-feathers). In fact in index.js there is also included JQuery 2.x what makes me think there might be some sort of incompatibility among them.
I already tried changing the project's dependency to JQuery 3.x but didn't help. Actually it will make even donejs develop fail (see CODE B).
I also tried the following:
cd my-app/node_modules/steal
npm install
but didn't help, another error appears and finally tried cd my-app/node_modules/can && npm install but that end up in multiple errors.
I'm using:
donejs#0.9.2
node#4.6.2
npm#2.15.11
can-connect-feathers#1.2.1
CODE A
NODE_ENV=production donejs start
my-app#0.0.0 start my-app
done-serve --proxy http://localhost:3030 --port 8080
done-serve starting on http://localhost:8080
Potentially unhandled rejection [5] TypeError: Error loading "package.json!npm" at file:my-app/package.json
Error loading "bundles/my-app/index" at file:my-app/dist/bundles/my-app/index.js
Error evaluating file:my-app/dist/bundles/my-app/index.js
Cannot read property 'createElement' of undefined
at i (file:my-app/dist/bundles/my-app/index.js:704:20)
at file:my-app/dist/bundles/my-app/index.js:1039:2881
at file:my-app/dist/bundles/my-app/index.js:1039:3580
at file:my-app/dist/bundles/my-app/index.js:268:21
at file:my-app/dist/bundles/my-app/index.js:268:27
at Object.exports.runInThisContext (vm.js:54:17)
at doEval (my-app/node_modules/steal/node_modules/steal-systemjs/dist/system.src.js:2059:10)
at __eval (my-app/node_modules/steal/node_modules/steal-systemjs/dist/system.src.js:1976:7)
at Loader.exec [as __exec] (my-app/node_modules/steal/node_modules/steal-systemjs/dist/system.src.js:339:5)
at Loader.loader.instantiate (my-app/node_modules/steal/node_modules/steal-systemjs/dist/system.src.js:1517:16)
CODE B
donejs develop
my-app#0.0.0 develop my-app
done-serve --develop --proxy http://localhost:3030 --port 8080
done-serve starting on http://localhost:8080
Potentially unhandled rejection [8] Error: Error loading "my-app#0.0.0#index.stache!done-autorender#0.8.0#autorender" at <unknown>
Error loading "can#2.3.27#util/jquery/jquery" at file:my-app/node_modules/can/util/jquery/jquery.js
Error loading "can#2.3.27#util/jquery/jquery" from "done-autorender#0.8.0#autorender" at file:my-app/node_modules/done-autorender/src/autorender.js
Did not find ./node_modules/can/node_modules/jquery/package.json
at FetchTask.utils.extend.next (file:my-app/node_modules/steal/ext/npm-crawl.js:532:11)
at file:my-app/node_modules/steal/ext/npm-crawl.js:556:33
at tryCatchReject (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:1183:30)
at runContinuation1 (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:1142:4)
at Fulfilled.when (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:930:4)
at Pending.run (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:821:13)
at Scheduler._drain (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:97:19)
at Scheduler.drain (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:62:9)
at nextTickCallbackWith0Args (node.js:436:9)
at process._tickCallback (node.js:365:13)
Potentially unhandled rejection [16] Error: Error loading "can#2.3.27#util/jquery/jquery" at file:my-app/node_modules/can/util/jquery/jquery.js
Error loading "can#2.3.27#util/jquery/jquery" from "my-app#0.0.0#index.stache!done-autorender#0.8.0#autorender" at file:my-app/src/index.stache
Did not find ./node_modules/can/node_modules/jquery/package.json
at FetchTask.utils.extend.next (file:my-app/node_modules/steal/ext/npm-crawl.js:532:11)
at file:my-app/node_modules/steal/ext/npm-crawl.js:556:33
at tryCatchReject (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:1183:30)
at runContinuation1 (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:1142:4)
at Fulfilled.when (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:930:4)
at Pending.run (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:821:13)
at Scheduler._drain (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:97:19)
at Scheduler.drain (my-app/node_modules/steal/node_modules/steal-systemjs/node_modules/steal-es6-module-loader/dist/es6-module-loader.src.js:62:9)
at nextTickCallbackWith0Args (node.js:436:9)
at process._tickCallback (node.js:365:13)
If the double jQuery installation is the issue, it should be resolved by version 2.0.0, which is exactly the same as the 1.0 version, but requires that you pass in a jQuery package as the jquery option. So, in addition to whatever else you had in your can-connect-feathers config, you'll need to provide the jquery option:
import $ from 'jquery'
import Feathers from 'can-connect-feathers';
new Feathers({
jquery: $
});