Issue with YAMCS quickstart example

[rjler]

Summary

Followed https://github.com/akhenry/openmct-yamcs#installation and get blank webpage

Steps to Reproduce

1. Installed and successfully started YAMCS quickstart

2. Followed the instructions from https://github.com/akhenry/openmct-yamcs#installation
   git clone https://github.com/akhenry/openmct-yamcs.git
   cd openmct-yamcs
   npm install
   npm run build:example
   npm start

3. Opened firefox to http://192.168.0.69:9000/
   Displays a blank black window

4. Opened the developer tools - displays the following:
   

Environment

npm -version
9.6.7
node -v
v18.17.1

Ubuntu 20.04

[ozyx]

@rjler
Thanks for raising this, we will investigate. In the meantime in order to unblock you, could you try using build:example:master to install the latest Open MCT and see if the quickstart example works for you?

Thanks again. Let us know if you run into any other issues.

[unlikelyzero]

@rjler this is a bug with our optional dependency checks. I have opened a PR to fix this

[rjler]

Thanks for help ...

npm run build:example:master
Fixed the initial issue but encountered 'missing taxonomy'

From the developer tools:

**Modified example/index.js ( changed localhost: to host ip ): **

**Working as expected: **

[unlikelyzero]

@rjler can you try using 0.0.0.0 instead of your host IP? It looks like there's a CORS issue

[rjler]

Modified example/index.js

const config = {
"yamcsDictionaryEndpoint": "http://0.0.0.0:9000/yamcs-proxy/",
"yamcsHistoricalEndpoint": "http://0.0.0.0:9000/yamcs-proxy/",
"yamcsWebsocketEndpoint": "ws://0.0.0.0:9000/yamcs-proxy-ws/",
"yamcsUserEndpoint": "http://0.0.0.0:9000/yamcs-proxy/api/user/",
"yamcsInstance": "myproject",
"yamcsProcessor": "realtime",
"yamcsFolder": "myproject",
"throttleRate": 1000,
"maxBatchSize": 15
};

Get missing:taxonomy

From dev tools:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://0.0.0.0:9000/yamcs-proxy/api/user/. (Reason: CORS request did not succeed). Status code: (null).

[ozyx]

@rjler how are you running yamcs? are you using the provided Makefile in quickstart to spin everything up via docker?

[rjler]

quickstart: From https://github.com/akhenry/openmct-yamcs?tab=readme-ov-file#prerequisites
followed the quickstart link to: https://github.com/yamcs/quickstart. The followed the instructions.
No docker involved, executing YAMCS quickstart and openMCT on the same Ubuntu host. Using Firefox, on a Mac, on the same network ( 192.168.0.xxx ) to access openMCT ( 192.168.0.69:9000 ).

[ozyx]

@rjler Thanks for the info. Seems like the non-docker workflow has broken due to some recent change-- will investigate. In the meantime, you may try the docker workflow and see if that fits your needs.

[unlikelyzero]

Looks like this was closed as a part of #466

[charlesh88]

The solution in #466 is a good workaround, but not a solution. Per @akhenry, we should:

1. Release a new version of Open MCT.
2. Immediately add a note to README.md that with the npm run build:example:master solution for users that encounter the problem as noted in this issue.