[SOLVED] frontendStateMachineEditor CHECKOUT ERROR when running ./update_nrp build


#1

Hello everyone,

I’m installing NRP from source on fresh Ubuntu 18.04.
The build command: ./update_nrp build stoped like below.

frontendStateMachineEditor
-------------------------
error: pathspec 'package.json' did not match any file(s) known to git.
frontendStateMachineEditor CHECKOUT ERROR

I ran the command: git fetch, but It doesn’t work.
What should I do to solve this problem?

Best regards,
Yanbaru


#2

Dear Yanbaru,

Happy to see that gzweb is fixed. I think you should set the default node to v8.

nvm alias default 8

The overall rule seems to be on Ubuntu 18: install both node 0.10 and 8 and set default to 8.
Please reclone gzweb after this change and rerun the buil and tell me how it goes. I’ll change the install doc accordingly.

Best regards
Axel


#3

Dear vonarnim,

Thank you for your advice again, but I still have problem with Node.js.
As your suggestion, I install node v0.10 and v8 by nvm. Also I set the default node to v8.

user1@c8fcbd9639bf:~/Documents/NRP/user-scripts$ nvm ls
-> v0.10.48
v8.17.0
default -> 8 (-> v8.17.0)
node -> stable (-> v8.17.0) (default)
stable -> 8.17 (-> v8.17.0) (default)
iojs -> N/A (default)
lts/* -> lts/erbium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0
lts/dubnium -> v10.22.1 (-> N/A)
lts/erbium -> v12.18.4 (-> N/A)

Although it seem appropriate, error with build step wasn’t solved.

ExDFrontend
-----------------------
npm ERR! Linux 4.19.76-linuxkit
npm ERR! argv "/home/user1/.nvm/v0.10.48/bin/node" "/home/user1/.nvm/v0.10.48/bin/npm" "dedupe"
npm ERR! node v0.10.48
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package acorn@5.7.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! Please include the following file with any support request:
npm ERR! /home/user1/Documents/NRP/ExDFrontend/npm-debug.log
ExDFrontend INSTALL ERROR

Would you give me more ideas to check what is incorrect with my environment?

Best regards,
Yanbaru


#4

Dear Yanbaru,

From the output of nvm ls it seems that even though the v8 is the default one, the v0.10 is the one which is being used. To fix that you can do

nvm use node

and then check again the output of nvm ls. This time the little arrow on the left of the version should be before the version v8. So from:

-> v0.10.48
v8.17.0

to

v0.10.48
-> v8.17.0

If you confirm that this is the case then you can try resuming the script execution.

Best regards,
Manos


#5

Dear ManosAngelidis,

Thank you for your replying.
Your suggestion:
:~/Documents/NRP/user-scripts$ nvm ls
v0.10.48
-> v8.17.0
default -> 8 (-> v8.17.0)
node -> stable (-> v8.17.0) (default)
stable -> 8.17 (-> v8.17.0) (default)
iojs -> N/A (default)
lts/* -> lts/erbium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0
lts/dubnium -> v10.22.1 (-> N/A)
lts/erbium -> v12.18.4 (-> N/A)

solve issue on ExDFrontend building.
However I got another issue on frontendStateMachineEditor that is same as this.

The order of building steps are like:
ExDFrontend -> SlurmClusterMonitor -> gzweb -> frontendStateMachineEditor

Based on this post, installing node v0.10 is necessary for building gzweb. Also, as you suggested, using node v8 is necessary for building ExDFrontend.

Do you have any other solution?

this is whole log of ./update_nrp build
update_nrp build_log.txt (198.7 KB)

Best regards,
Yanbaru


#6

Hi everyone.
I solved this issue by recloning frontendStateMachineEditor in ~/Documents/NRP/ or $HBP.
The error log said about package.json. I checked files in $HBP/frontendStateMachineEditor and found that there is no package.json file. I think I had something wrong with the cloning step.
Therefore, the solution is like

sudo rm -r $HBP/frontendStateMachineEditor
cd $HBP/user-scripts
./clone-all-repos

Thanks a lot for taking your time!!