installation

[ASamSam]

Hello
i would like to try FRET, but i cannot install it.
I did try steps described for Windows 10 - it fails

131 timing stage:runTopLevelLifecycles Completed in 764ms
132 verbose stack ZlibError: zlib: unexpected end of file
132 verbose stack     at Zlib.(anonymous function).onerror (C:\Users\andre\AppData\Roaming\nvm\v10.15.0\node_modules\npm\node_modules\minizlib\index.js:131:21)
132 verbose stack     at Unzip.write (C:\Users\andre\AppData\Roaming\nvm\v10.15.0\node_modules\npm\node_modules\minizlib\index.js:255:31)
132 verbose stack     at Unzip.flush (C:\Users\andre\AppData\Roaming\nvm\v10.15.0\node_modules\npm\node_modules\minizlib\index.js:222:10)
132 verbose stack     at Unzip.end (C:\Users\andre\AppData\Roaming\nvm\v10.15.0\node_modules\npm\node_modules\minizlib\index.js:229:10)
132 verbose stack     at Object.end (C:\Users\andre\AppData\Roaming\nvm\v10.15.0\node_modules\npm\node_modules\tar\lib\parse.js:415:21)
132 verbose stack     at PassThrough.onend (_stream_readable.js:628:10)
132 verbose stack     at Object.onceWrapper (events.js:273:13)
132 verbose stack     at PassThrough.emit (events.js:187:15)
132 verbose stack     at endReadableNT (_stream_readable.js:1094:12)
132 verbose stack     at process._tickCallback (internal/process/next_tick.js:63:19)
133 verbose cwd C:\windows\system32
134 verbose Windows_NT 10.0.19045
135 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--global" "windows-build-tools"
136 verbose node v10.15.0
137 verbose npm  v6.4.1
138 error code Z_BUF_ERROR
139 error errno -5
140 error zlib: unexpected end of file
141 verbose exit [ -5, true ]

then i did try install it on ubuntu with the docker solution - it fails on compilation.

then i did try to get sources from repository :

same happens with release 3.0 zip
how i can manage to install it?

[andreaskatis]

Hi @ASamSam ,

Thank you for checking out FRET!

For methods 1 and 3 (Windows 10 and directly from source in Ubuntu), please provide us with more information regarding the step in the guide, in which you encounter the issues. For Ubuntu, it appears that a log file was created (last line of the error output in your Ubuntu screenshot), so you can just attach that. Similarly for Windows, if a log file was created, please send it to us. If not, just mentioning at what step in the guide the issue occurred would help.

In the meantime, I will check out the docker installation method, and get back to you.

Andreas

[ASamSam]

windows node js 16.log
log ubuntu.txt
windows node js 10.log

here are log files.
on windows there are two log files:
node js 10: fails: npm install --global windows-build-tools
(it reports something like - npm WARN deprecated [email protected]: Node.js now includes build tools for Windows. You probably no longer need this tool. See https://github.com/felixrieseberg/windows-build-tools for details.)
+
node js 16: fails:npm run fret-install

ubuntu:
npm run fret-install

[andreaskatis]

Hi @ASamSam ,

Thank you for the additional info. I wanted to post a small update regarding what I've observed so far.

• It appears that since Node.js now includes Windows build tools, the corresponding command to install the windows-build-tools may have been deprecated. I tried to run npm install --global windows-build-tools yesterday, but it looks like it is running for an abnormally long time. As a result, I have not been able to replicate the exact output that you've provided with your log files. I will try another clean version of Windows today and see if that works.
• Furthermore, for your node 16 log file, the error message was error Maximum call stack size exceeded. Looking up online for solutions, it appears that this may occur when the Javascript call stack cannot add any more function calls. A solution is to clean your cache by running npm cache clean --f, and running npm run fret-reinstall.
• For the Ubuntu installation, looking at the log file, it appears that node version 12.22.9 is actually being used to install FRET. Please make sure that a version between 15.14.x and v16.16.x is used instead, as these are the versions we currently know for sure that the installation works with.
• Final note when trying to install from source in Windows/Ubuntu: If the installation fails at any point, I would recommend applying the solution to a freshly downloaded copy of the repository, to prevent the previous installation attempt from affecting subsequent attempts.

Please let me know if any of the above helped with your installation issues so far. I'm currently working on an updated version of the docker image that should be functional again. Thank you very much for letting us know of these issues!

Best Regards,

Andreas

[andreaskatis]

Hi @ASamSam,

We have a note related to the GPU-related issue in our installation instructions. To fix it you need to do the following:

1. cd fret/fret-electron
2. Open package.json in an editor
3. Find the "scripts" object, change the value of the "start" key from "cross-env NODE_ENV=production electron ./app/" to "cross-env NODE_ENV=production electron --no-sandbox ./app/"
4. Save and exit the editor
5. npm start

The IO errors seem to be happening because of multiple instances of the app running at the same time. Try applying the fix above and see if they persist. If they do, one straightforward way to get back to a clean state would be to delete the 'fret-db' and 'model-db' folders under '/home/asam/Documents'. Please be aware though that deleting the folders will also permanently delete any current projects or requirements that you have created in FRET (which I assume you haven't done since you haven't been able to open the application in the first place).

[ASamSam]

thank you for the fast reply, going to try.
btw, I have new windows log:

win.txt

[ASamSam]

thanks! seems your description of multiple instance helps: previously I found 'fret-linux64' in executables. It was not able to save anything but something was working. and maybe it gives the problem. i did restart machine and after that was able to run

[andreaskatis]

Hi @ASamSam,

thank you for the fast reply, going to try. btw, I have new windows log:

[win.txt](https://github.com/NASA-SW-VnV/fret/files/12775107/win.txt

Looking at the new Windows log file I noticed two issues:

1. At some point the script tries to download dependencies from github, but fails to do so because it couldn't access the site. Please make sure that the machine can indeed access github.com
2. There was another issue related to node-gyp. What version of python are you using? If it is 3.11 or later, please try switching to 3.10. To set the python version that npm will use you can run 'npm config set python /full/path/to/new/python/binary'

[ASamSam]

the machine should be able to connect to github, it is the one I use for everything.
yet yes, I do use Python 3.11
maybe I can try python 3.10 later, right now ubuntu solution works for me.
Thank you very much