Repository navigation
Includes 2.6.1 to 2.6.7.
Changed
- The screen waits for the server when Root restarts the app. On 27 and 28 October Root restarted the app about 200 times in all five communities: its community service did not answer (
UNAVAILABLE), or it asked the app to shut down (Hub is disconnecting). In both cases the Root SDK ends the server process itself, so the app cannot stop it. Now the title list, the movie nights and the settings are asked again when the server does not answer, after 1, 2, 4, 8 and 15 seconds (plus up to half of that at random), which covers a restart (about 15 seconds). Errors that come from the app's own rules still show at once, and nothing that writes is ever repeated - The server shuts down cleanly when Root asks. It stops the movie-night sweeper and closes the database before leaving, and writes a line to the startup log, so a requested shutdown can be told apart from a crash
Added
- Startup log (2.6.6). The server writes each step of its startup (loading, database, settings, nights, covers, services) and any unhandled error to the server output and to the app log that community admins see in Root
Fixed
- Updates could leave the app unavailable in Root (2.6.2 and 2.6.3). The upload package carried the whole
node_modulesfolder (59 MB) and the Root portal timed out while processing it. It is now built with only what the server needs at run time (about 5 MB), including the libraries thatsqlite3loads when it starts
2.6.1, 2.6.4 and 2.6.5 carried no new code: they were sent again with a new number while an upload or a community was stuck.
Full history: CHANGELOG.md