File

mod_compliance_latest: Gracefull error logging on missing dependency. diff --git a/mod_compliance_latest/README.md b/mod_compliance_latest/README.md --- a/mod_compliance_latest/README.md +++ b/mod_compliance_latest/README.md @@ -9,13 +9,15 @@ rockspec: # Introduction -This module will always require and load to the lastest compliance tester we have in the community modules. -Currently this is [mod_compliance_2023]. +This meta-module will always `require` (and therefore auto-load) the lastest compliance tester we have in the community modules. +Currently this is [mod_compliance_2023]. See the linked module for further details. + +If you do not use the *Prosody plugin installer* this module will likely have limited value to you. +You can also just install the current compliance tester manually. # Configuration -Just load this module as any other module and it will automatically install [mod_compliance_2023] if you use the Prosody plugin installer. -See the linked module for further details. +Just load this module as any other module and it will automatically install and load [mod_compliance_2023] if you use the *Prosody plugin installer*. # Compatibility diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua --- a/mod_compliance_latest/mod_compliance_latest.lua +++ b/mod_compliance_latest/mod_compliance_latest.lua @@ -1,1 +1,6 @@ -module:depends("compliance_2023"); +local success, err = pcall(function() module:depends("compliance_2023") end) + +if not success then + module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?") + return 1, "Error: Couldn't load dependency mod_compliance_2023." +end

::: {.alert .alert-warning}
This module is an experiment about a more graceful shutdown process.

Graceful shutdown has now been implemented in Prosody trunk and will be
part 0.12. See [issue #1225](https://issues.prosody.im/1225) for
details.
:::

Why
===

When shutting down, a number of sessions, connections and other things
are teared down. Due to all these things happening very quickly,
sometimes e.g. client unavailable notifications don't make it to all
remote contacts because the server-to-server connections are teared down
just after.

How
===

This module works by breaking the shutdown process into separate steps
with a brief pause between them.

It goes something like this

1.  Stop accepting new client connections.
2.  Close all client connections.
3.  Fire event for everything else.
4.  Tell `net.server` to quit the main loop.
5.  ???
6.  Still here? Kill itself.