Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A couple seemingly harmless exceptions #1081

Open
kyle-kingsbury opened this issue May 5, 2023 · 0 comments
Open

A couple seemingly harmless exceptions #1081

kyle-kingsbury opened this issue May 5, 2023 · 0 comments

Comments

@kyle-kingsbury
Copy link
Contributor

After running systemctl restart fabmo, sometimes, there is this exception:

error: Error: [object Object] is not a valid profile.
at Object.apply (/fabmo/profiles.js:260:18)
at EngineConfig.update (/fabmo/config/engine_config.js:76:18)
at EngineConfig. (/fabmo/config/config.js:170:18)
at /fabmo/node_modules/graceful-fs/graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) [config]

If you are at the login screen and you refresh the page this one shows up. It makes sense, since no one is logged in that there would be no user information:
error: Error: no user
at /fabmo/routes/websocket.js:37:27
at /fabmo/authentication.js:327:13
at UserConfig.findOne (/fabmo/config/user_config.js:239:16)
at Object.exports.getUserById (/fabmo/authentication.js:317:17)
at Array. (/fabmo/routes/websocket.js:35:28)
at run (/fabmo/node_modules/socket.io/dist/namespace.js:124:19)
at Namespace.run (/fabmo/node_modules/socket.io/dist/namespace.js:135:9)
at Namespace._add (/fabmo/node_modules/socket.io/dist/namespace.js:211:14)
at processTicksAndRejections (node:internal/process/task_queues:96:5) [websocket]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant