MagicMirrorOrg
Async node_helper start()
If a node_helper uses an async method for start(), it appears that MagicMirror declares the system ready as soon as the function returns the initial Promise. It would be nice if MM would collect the promises from the various modules, then await Promise.all(...) of them.
Steps to Reproduce: Use the async/await pattern within a node_helper's start() method
Expected Results: Initialization completes when all node_helpers are done initializing
Actual Results: MagicMirror reports ready while node_helper is still printing loading status to console
I've been trying to use it in my own module, MMM-Powerwall. I borrowed logic from MMM-RemoteControl that reads config files off the disk, and I'd already used the async file access methods elsewhere.
but u only need to use async functions if u intend to use await. which is similar to using sync calls. there are a few different approaches to using async and await without doing it with start. you can start a timer, or use the notification call from module to node helper.
Hi @MikeBishop finally came around to look at some old issues, and whipped up a PR for your suggestion. Seems to work on my local setup but I want to get a little feedback first before I proceed.
So there's apparently an issue with waiting for modules that take a long time. It looks like if initialization of the modules gets pushed out past a certain point in electron's loading process, electron will display a blank screen locally. Accessing with a browser works fine, because everything initialized by then.
I think I have a clean repro of the issue in https://github.com/MikeBishop/MMM-asyncdeath – the synchronous start function produces this in the logs and loads normally:
[21.01.2023 14:55.02.692] [LOG] Synchronous start-up -- all is well
[21.01.2023 14:55.02.693] [LOG] Sockets connected & modules started ...
[21.01.2023 14:55.03.235] [LOG] Launching application.
The async start function produces this in the logs and fails:
[21.01.2023 14:52.54.143] [LOG] About to break by using await
[21.01.2023 14:52.54.884] [LOG] Launching application.
[21.01.2023 14:52.56.512] [LOG] Sockets connected & modules started ...
Note the reversed order of “Launching application” and “modules started”. Seems feasible this could also happen with a synchronous module startup that takes a long time, but I haven’t tested that.
Seems like there's an additional step needed here to delay Electron's startup until the modules are done loading.
A quick look before bedtime makes me think the problem only occurs when starting MM with electron and not when in servermode?
Seems like electron.js calls createWindow (when the electron app is "ready") but config isnt yet set (in the start callback at the end) due to the async nature....
A quick look before bedtime makes me think the problem only occurs when starting MM with electron and not when in servermode?
Correct -- web browsers connecting once everything finishes startup are fine. I think it's probably that electron launch fails (or fails to connect) and then never retries. If so, perhaps rather than delaying electron start-up, we could kick electron to retry once the backend is ready.
I dont like delaying stuff arbitrarily since we dont know how long some modules might take. Maybe my PR solution is enough and a little more future-proof
Belated, but I reverted the work-around in my module and cherry-picked in this change, and MM is able to start up properly.