I get this error when I run npm start

[nasa-sw-vnv]

I get this error when I run npm start

[andreaskatis]

Hi @EliasH-NMBU ,

Yes, this error message is probably not related to the discrepancies in the exported code that you are noticing.

Is Tage Andersen the colleague that you are referring to? If yes, Tage mentioned that you have tried running FRET in two ways: 1) building and starting the application from source (npm run fret-install && npm start) and 2) using a pre-built executable that we have available here:

https://github.com/NASA-SW-VnV/fret/tree/master/executables

The pre-built executable is outdated, so if you are comparing exported code between it and the latest source in the master branch, you will definitely notice differences, not only in exported code but also other features. We are actually planning to remove the pre-built binary entirely from the repository in the near future.

Currently, we recommend either building from source or, if you still want to use a MacOS or Linux executable, you can build one using the scripts that we provide here:

https://github.com/NASA-SW-VnV/fret/tree/master/tools/Scripts/FRETExecutables

An additional option for Linux, is to build said executable using a Docker image. As a result, you would only need to have docker installed on your Linux environment, as the image takes care of all other dependencies needed to build the executable. Do note though that optional dependencies like NuSMV, Z3, jkind and Kind 2 will still need to be installed in your host OS environment, and added to your PATH environment variable. You can find the Docker guide here:

https://github.com/NASA-SW-VnV/fret/blob/master/fret-electron/docs/_media/installingFRET/installationInstructions.md#build-executable-with-docker-image

With the above being said, if your issues persist while using the above recommended ways to install and use FRET, please do let us know. The more details that you can provide on how we can replicate the issue, the better.

Best Regards,

Andreas

[andreaskatis]

Hi @EliasH-NMBU,

Thanks again for your interest in using FRET. Can you give us some more details as to the environment that you are using to run FRET i.e. whether it is Linux or MacOS, and the exact distribution and version? In the case of MacOS, please also tell us the machine's architecture i.e. whether it is x64 or arm64.

Also, it would help us if you could send a copy of the entire output of the terminal when running npm start. If any log files are created, please send those as well.

Best Regards,

Andreas

[EliasH-NMBU]

I am on jammy (Ubuntu 22.04.3, linux). Will share more info tomorrow.

[anmavrid]

Thanks, @EliasH-NMBU. Also, please share the node and python versions that you are using.

[andreaskatis]

@EliasH-NMBU , the issue seems to be related to the electron package. In addition to what we've asked above, please also let us know the version of electron that your installation is using. To do this, run the following command under fret/fret-electron

npm list electron

and send us the output.

[EliasH-NMBU]

Using the "npm list electron" gave me the following output:

fret/fret-electron$ npm list electron
[email protected] /home/eliash/ros2_ws/src/fret/fret-electron
├─┬ @electron/[email protected]
│ └── [email protected] deduped
└── [email protected]

When running npm start the program opens, but I wonder if some FRET issues I have been having is related to the error on the last line of the output:

fret/fret-electron$ npm start

[email protected] prestart
npm run build

[email protected] build
concurrently "npm run build-main" "npm run build-renderer"

[0]
[0] > [email protected] build-main
[0] > cross-env NODE_ENV=production node --trace-warnings -r @babel/register ./node_modules/webpack/bin/webpack --config webpack.config.main.prod.js
[0]
[1]
[1] > [email protected] build-renderer
[1] > cross-env NODE_ENV=production node --trace-warnings -r @babel/register ./node_modules/webpack/bin/webpack --config webpack.config.renderer.prod.js
[1]
[0] asset ./app/main.prod.js 2.65 MiB [compared for emit] [minimized] (name: main) 2 related assets
[0] orphan modules 9.87 KiB [orphan] 16 modules
[0] runtime modules 1.04 KiB 5 modules
[0] modules by path ./node_modules/ 2.04 MiB 444 modules
[0] modules by path ./support/ 300 KiB 34 modules
[0] modules by path ./app/ 2.02 MiB 28 modules
[0] modules by path ./model/ 129 KiB
[0] modules by path ./model/fretDbSupport/.js 21 KiB 5 modules
[0] modules by path ./model/modelDbSupport/.js 29.9 KiB 4 modules
[0] + 3 modules
[0] modules by path ./analysis/*.js 46.5 KiB
[0] ./analysis/connected_components.js 10 KiB [built] [code generated]
[0] ./analysis/realizabilityCheck.js 7.28 KiB [built] [code generated]
[0] ./analysis/DiagnosisEngine.js 25.9 KiB [built] [code generated]
[0] ./analysis/HSNode.js 3.27 KiB [built] [code generated]
[0] + 17 modules
[0] webpack 5.89.0 compiled successfully in 12429 ms
[0] npm run build-main exited with code 0
[1] assets by status 1.56 MiB [cached] 34 assets
[1] assets by status 5.08 MiB [compared for emit]
[1] asset renderer.prod.js 5.03 MiB [compared for emit] [minimized] (name: main) 2 related assets
[1] asset style.css 49 KiB [compared for emit] (name: main)
[1] Entrypoint main 5.08 MiB (14.9 MiB) = style.css 49 KiB renderer.prod.js 5.03 MiB 35 auxiliary assets
[1] orphan modules 2.39 MiB [orphan] 1231 modules
[1] runtime modules 1.04 KiB 5 modules
[1] modules by path ./node_modules/ 7.04 MiB (javascript) 36.5 KiB (css/mini-extract)
[1] javascript modules 7.04 MiB 1548 modules
[1] json modules 2.03 KiB 3 modules
[1] css ./node_modules/css-loader/index.js!./node_modules/font-awesome/css/font-awesome.css 36.5 KiB [built] [code generated]
[1] modules by path ./app/ 2.65 MiB (javascript) 12.5 KiB (css/mini-extract) 98 modules
[1] modules by path ./support/ 390 KiB 34 modules
[1] modules by path ./docs/_media/ 367 KiB
[1] modules by path ./docs/_media/user-interface/examples/ 10.6 KiB 6 modules
[1] ./docs/_media/fretishGrammar/index.html 339 KiB [built] [code generated]
[1] ./docs/_media/ExportingForAnalysis/analysisInsideFRET.md 4.98 KiB [built] [code generated]
[1] ./docs/_media/exports/realizability.md 12.2 KiB [built] [code generated]
[1] + 14 modules
[1] webpack 5.89.0 compiled successfully in 34565 ms
[1] npm run build-renderer exited with code 0

[email protected] start
cross-env NODE_ENV=production electron ./app/

We can use PouchDB with LevelDB!
Initial base properties have been persisted.
[73781:0208/092202.398837:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

Node and python versions:
node -v
v18.19.0
python3 --version
Python 3.10.12

[andreaskatis]

Thank you, @EliasH-NMBU . Can you please describe the issues that you are experiencing? I originally thought that the error was preventing the app from starting.

[EliasH-NMBU]

Apologies for the confusion.
My FRET seems to work mostly well. I have added z3 for realizability functions, but my exported json code has an altered layout from my friends FRET system. So was wondering if this error could have something to do with it.
I assume not, but thought to check if this was a common error message to get when launching the 'npm start'.
Will do some more tests tomorrow and if the issue continues I will post json export info here from my and his system.
If not, then I will assume this error does not affect an important part of the software.

[anmavrid]

I am closing this issue as resolved. To avoid confusion, we have removed the older executables from this repo. We do provide scripts for building FRET executables for different systems and a Docker image for Linux systems.