I am creating my first substrate chain (online tutorial).
Installed node.js and yarn - and attempting to start node in development mode <./target/debug/node-template --dev --tmp>,
when I run code keep getting error -
no such file or directory...
Obviously, I am doing something wrong, and would like to know how to solve this issue?
I can think of two possible scenarios as to why you encountered the said issue:
Since ./target/debug/node-template is a relative path, you have to be on the ditectory where the target folder is located in
Build your node-template using cargo build
Thanks for your reply.
I have built and compiled the Node Template [substrate-node-template] using [cargo build] ...
I checked the folder [substrate-front-end-template] to ensure that [yarn] and [node.js] are installed:
versions installed - yarn 1.22.5 / node 12.18.4
In [substrate-front-end-template] directory I run following code:
./target/debug/node-template --dev --tmp
Receive error 'is not recognized as the name of a cmdlet function......' –
Is the target folder located where I have installed yarn and node.js?
Related
Recently I've upgraded my node version to 16.15.1. Before the node upgrade I used a 1.x yarn version. Now I want to use yarn v3.2.x in my project.
Normally this would be achieved by executing the command yarn init -2 in the console. This would generate a .yarn/releases folder in my project where the yarn-[version].cjs is stored. Furthermore, in the project .yarnrc.yml the line yarnPath: .yarn/releases/yarn-[version].cjs is added.
However, I have the problem that I work in a closed working environment. When I execute the command yarn init -2 I get problems with the proxy.
This is the error I get:
error An unexpected error occurred: "https://github.com/yarnpkg/berry/raw/master/packages/yarnpkg-cli/bin/yarn.js: connect ECONNREFUSED xxx.x".
I tried to set the proxy in the project and also in the user .yarnrc.yml but both didn't seem to work.
My question is whether there is a possibility to add a proxy url to the yarn init -2 command, e.g. via a cmd flag?
Yes, you can specify a proxy to use during installation. Add httpProxy or httpsProxy to yarnrc.yml.
While installing the hybris, my localextension.xml is creating in comment form. I am very new in hybris ecommerce development.
So I have followed below steps for installing the hyrbis -
Installed the zip version of Hybris 6.6
Unzip it
From Platform folder, I opened the terminal and ran ". ./setantenv.sh" And after that I ran "ant clean all" and after the build completed succesfully all folders got created in Hybris folder.
Then I ran "./hybrisserver.sh" and my server got started successfully.
Then I ran "https://localhost:9002/" over that I initialize and it also went successfully.
When I try to access hmc or backoffice it is giving me 404 page not found error.
I checked my localextension.xml file and found all the extensions generated as a comment as shown below.
Could anyone help me out where I am doing the mistake.
Thanks in advance.
If you are using original package you need to install a receipt. Go to install folder.
Run below command for listing existing receipt
./install.sh -l
Prepare b2c with acc:
./install.sh -r b2c_acc
Initialize b2c with acc (Also you can use ant clean all for this step):
./install.sh -r b2c_acc initialize
Start hybris (Also you can use ./hybrisserver.sh start for this step):
./install.sh -r b2c_acc start
When you do "ant all" for the first time and set-up the config folder, it generates a localextensions.xml file which contains extensions that are commented out. If you initialize and start Hybris using this setting, you get nothing, except the HAC.
To enable HMC, you need to at least have "platformhmc" extension enabled (i.e. not commented out) in localextensions. So, stop Hybris, uncomment platformhmc, and do another build (i.e. "ant all"). After that, you can do a Platform Update, or a Platform Initialize (to build from scratch again). When it's done, and you've started Hybris, HMC should be accessible.
Or, if you want more features enabled by default, you can do #mkysoft's suggestion and use recipes.
I am trying to deploy a react app bootstrapped with create-react-app to heroku. The build keeps failing, and I get this error on the command line and in the build log
App not compatible with buildpack:
https://github.com/AdamT213/RateYourAcquaintance.git
bash:
/app/tmp/buildpacks/85d7c3f242750d8981190d9ed3f29461a37d776664b86f3dc3263563e08c29443b03b01355b70cb2a4a461abab934f47aa7919c42b019918961b2ebf902b1fa/bin/detect
No such file or directory
More info: https://devcenter.heroku.com/articles/buildpacks#detection-
failure
! Push failed
What does this mean?
Okay, I see now. I was trying to set my app's url as the buildpack, when I really need this url: https://github.com/mars/create-react-app-buildpack.git. Makes sense now!
I would also advise checking what files the gitignore file are ignoring. In particular, the "BUILD" folder needs to not be ignored (and it seems it is by default for me)
I am trying to set up a canvas lms on an amazon ec2 Ubuntu environment. I've gone so far until the file generation step of the production environment guide. I've been able to successfully follow the steps until this point.
Steps to reproduce:
I was successful in making the asset directories and taking their ownership as directed in this step:
sysadmin#appserver:~$ cd /var/canvas
sysadmin#appserver:/var/canvas$ mkdir -p log tmp/pids public/assets public/stylesheets/compiled
sysadmin#appserver:/var/canvas$ touch Gemfile.lock
sysadmin#appserver:/var/canvas$ sudo chown -R canvasuser config/environment.rb log tmp public/assets \ public/stylesheets/compiled Gemfile.lock config.ru`
After this, I run 'npm install'
It is at this point that after getting some deprecated warnings I get stuck at this line:
canvas-lms#0.0.0 preinstall /home/ubuntu/canvas/script/gem_npm install
running npm install for gems/canvas_i18nliner/package.json
running npm install for gems/selinimum/package.json
Killed [ ..] / extract:lodash: sill gunzTarPerm modified mode [ 'fp/getOr.js', 420, 436 ]'
What I've already tried:
First I thought it was an error with the port 9418/tcp not being open. I opened this port through amazon ec2 security group inbound rules. This did not work. Then I tried opening all the ports 1-65000 to fix this. It still did not work.
Additional notes:
From the looks of it, it does not looks like a port issue because the script is able to fetch data in the previous steps. Also from the progress bar it can be seen that the extract is failing only when the last 2 dots are left as the progress bar is shows like this: [ ..]. I'm guessing this is a .js creation erorr.
The documentation provides a link to fix those issues but the description of the steps to follow are not very elaborate there as I can't understand what exactly i need to do. Can someone please look into this and help me? Any help is much appreciated.
The File Generation section in the production guide says to follow this link to fix .js creation issues. The solution I found in this link was to add the following code to the compile_template function found in lib/handlebars/handlebars.rb file. The directory lib/handlebars does not exist in /lib
def compile_template(source, id, plugin=nil)
require 'execjs'
require 'multi_json'
P.S. I downloaded my installation directly from the git repository so no chance of this being missing for some reason :/
I'm new to Mesos. I would like to know how do I know whether Mesos master is set up correctly in the node?
I have follow the set up given by http://mesos.apache.org/gettingstarted/
I am unable to run the following command:
Comment: Start mesos master (Ensure work directory exists and has proper permissions).
$ ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
but it shown error given:
./bin/mesos-master.sh: line 24: /home/user/mesos-0.20.0/build/src/mesos-master: No such file or directory
What ways should I proceed?
First, a few questions to help us debug your build:
Did the mesos build (make) complete successfully, and did make check pass all the tests?
If /home/user/mesos-0.20.0/build/src/mesos-master does exist, do you have execute permissions on it?
Are you running ./bin/mesos-master.sh from within /home/user/mesos-0.20.0/build/, or did you move the directory elsewhere?
If this is your first attempt at Mesos and you just want to run it and try it out (rather than fix bugs and develop features for it). I would recommend using a pre-built or cloud-deployed version of Mesos, rather than trying to build it yourself. See:
http://mesosphere.com/downloads/
http://mesosphere.com/downloads/details/index.html#apache-mesos
I'd suggest to follow Mesos Getting Started documentation.
After your system requirements are satisfied, following the section:
System Requirements
Once you reach the following section:
Building Mesos
when you execute the make without disabling verbosity, ensure that all process completed successfully. If it stops (e.g. tipically for proxy related issues) try to fix it accordingly or otherwise post your stack somewhere and I would be happy to help (if I can).
Unfortunately, running make check could not reveal the problem sometimes.
Have you run the make check command ? It is said in the documentation that the binaries will only be available after running the make checkcommand.Ì faced the same issue and it was because i didn't run that command.