prosody-modules
2e33eeafe962
mod_traceback/README.markdown

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody-modules

Annotate

mod_traceback/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parent 2799:db0f654b9b3f
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
2799
db0f654b9b3f mod_traceback: Add a brief README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
1 This module writes out a traceback to `traceback.txt` in Prosodys data
db0f654b9b3f mod_traceback: Add a brief README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
2 directory (see `prosodyctl about`) when the signal `SIGUSR1` is
db0f654b9b3f mod_traceback: Add a brief README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
3 received. This is useful when debugging seemingly frozen instances in
db0f654b9b3f mod_traceback: Add a brief README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
4 case it is stuck in Lua code.