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

---
labels:
- Stage-Obsolete
---

# Introduction

::: {.alert .alert-warning}
This behavior has now been merged into
[mod_s2s][doc:modules:mod_s2s] in trunk and is therefore obsolete
when used with trunk.

It can still be used with Prosody 0.12 to get this behavior.
:::

This module closes s2s connections when
[mod_smacks][doc:modules:mod_smacks] reports that a connection has not
received a timely acknowledgement as requested, indicating that the
connection is broken or the remote server is not responding.

With the connection closed, the next stanza to be directed to that
server will trigger Prosody to establish a new connection, instead of
queueing it on the potentially broken connection.

This should prevent messages from being stuck in a queue for a
potentially long time before being bounced back to the sender as
delivery failure reports.

Normally the amount of time it takes for a broken connection to time out
is determined by TCP.

If this is deemed sensible behavior then it will likely be merged into
Prosody itself somewhere.