You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing issues with Coral while setting everything up locally on my machine as advised by the docs.
Everything seems to work, until I am running npm run watch.
The command itself will not fail, but it will output an error inbetween: @coralproject/[email protected] generate:relay:account ts-node --transpile-only ./scripts/compileRelay --bundle account Ignore watch: [ './docs/' ] Using ts-node version 9.1.1, typescript version 3.9.5 TypeError: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js at new NodeError (node:internal/errors:372:5) at Object.watch (node:fs:2262:11) at add (/home/ihardyslide/git/talk/node_modules/filewatcher/index.js:74:34) at /home/ihardyslide/git/talk/node_modules/filewatcher/index.js:93:5 at FSReqCallback.oncomplete (node:fs:199:5) Debugger listening on ws://127.0.0.1:9229/540ab85a-227b-44d8-a8d4-7428f46b9bf1 For help, see: https://nodejs.org/en/docs/inspector Command exited with 1
In the end, everything will seem to run through and listen, but actually Coral was never started in the first place.
This behaviour can be examined, while trying to go to the /admin or /install page.
You will get an endless reload loop, because all connections to Coral on the exported $PORT will fail with a Connection Refused error, e.g.: [HPM] Error occurred while trying to proxy request /embed/bootstrap from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /api/story/count.js?callback=CoralCount.setCount¬ext=false&ref=ZmFsc2U7aHR0cDovL2xvY2FsaG9zdDo4MDgwL3N0b3J5Lmh0bWw%3D&url=http%3A%2F%2Flocalhost%3A8080%2Fstory.html from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /embed/bootstrap from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /admin from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /install from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
It is more obvious, when you start the npm run start:development script, because this one will fail and won't stay executing.
I rolled back to Node 13.13.0 (via NVM), did a npm ci again, did npm run watch again, suddenly the error message is gone and Coral boots up as expected and I can enter the /install and /admin screen as expected.
Also the script npm run start:development runs through smoothly then.
Expected behavior:
Coral starts as it should, when running npm run watch on Node 16 LTS
Actual behavior:
Coral does not start at all, when running npm run watch on Node 16 LTS
Hi,
I am experiencing issues with Coral while setting everything up locally on my machine as advised by the docs.
Everything seems to work, until I am running npm run watch.
The command itself will not fail, but it will output an error inbetween:
@coralproject/[email protected] generate:relay:account
ts-node --transpile-only ./scripts/compileRelay --bundle account
Ignore watch: [ './docs/' ]
Using ts-node version 9.1.1, typescript version 3.9.5
TypeError: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js at new NodeError (node:internal/errors:372:5) at Object.watch (node:fs:2262:11) at add (/home/ihardyslide/git/talk/node_modules/filewatcher/index.js:74:34) at /home/ihardyslide/git/talk/node_modules/filewatcher/index.js:93:5 at FSReqCallback.oncomplete (node:fs:199:5)
Debugger listening on ws://127.0.0.1:9229/540ab85a-227b-44d8-a8d4-7428f46b9bf1
For help, see: https://nodejs.org/en/docs/inspector
Command exited with 1
In the end, everything will seem to run through and listen, but actually Coral was never started in the first place.
This behaviour can be examined, while trying to go to the /admin or /install page.
You will get an endless reload loop, because all connections to Coral on the exported $PORT will fail with a Connection Refused error, e.g.:
[HPM] Error occurred while trying to proxy request /embed/bootstrap from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /api/story/count.js?callback=CoralCount.setCount¬ext=false&ref=ZmFsc2U7aHR0cDovL2xvY2FsaG9zdDo4MDgwL3N0b3J5Lmh0bWw%3D&url=http%3A%2F%2Flocalhost%3A8080%2Fstory.html from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /embed/bootstrap from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /admin from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /install from localhost:8080 to http://localhost:6789 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
It is more obvious, when you start the npm run start:development script, because this one will fail and won't stay executing.
After digging into, I came to this issue.
This comment was my rescue.
I rolled back to Node 13.13.0 (via NVM), did a npm ci again, did npm run watch again, suddenly the error message is gone and Coral boots up as expected and I can enter the /install and /admin screen as expected.
Also the script npm run start:development runs through smoothly then.
Expected behavior:
Coral starts as it should, when running npm run watch on Node 16 LTS
Actual behavior:
Coral does not start at all, when running npm run watch on Node 16 LTS
Related Issues:
wclr/ts-node-dev#143
Versions:
The text was updated successfully, but these errors were encountered: