Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | mod_mam: Prefer not archiving if no interesting payloads are found | Kim Alvefur | 2020-04-21 | 1 | -1/+3 |
| | |||||
* | mod_mam: Check sender of error instead of receiver | Kim Alvefur | 2020-04-21 | 1 | -0/+3 |
| | | | | | | The intent is to capture errors to stanzas sent by the local user, so that they can see why a message failed to be delivered even if the error came after they went offline. | ||||
* | mod_mam: Store XEP-0184 receipts and requests | Kim Alvefur | 2020-04-21 | 1 | -0/+5 |
| | | | | Happy now Ge0rG? | ||||
* | mod_mam: Add more positive hints for storage | Kim Alvefur | 2020-04-21 | 1 | -0/+12 |
| | | | | Mostly just lifted from mod_csi_simple | ||||
* | mod_mam: Rework hints handling | Kim Alvefur | 2020-04-21 | 1 | -7/+6 |
| | | | | Improved readability and early returns definite yes/no answer. | ||||
* | mod_mam: Invert check for type | Kim Alvefur | 2020-04-21 | 1 | -5/+13 |
| | | | | | This is based on code in mod_csi_simple and aiming towards being more flexible and maintainable than a couple of tests for when not to store. | ||||
* | mod_mam: Log 'why' a stanza is archived | Kim Alvefur | 2020-04-21 | 1 | -1/+1 |
| | | | | | Logging of 'why not' is already done. Why not both? Will make more sense when the rules evolve a bit. | ||||
* | mod_mam: Factor out "should we store this" into a function | Kim Alvefur | 2020-04-21 | 1 | -13/+21 |
| | | | | | Meant to improve readability and ease further improvements to this algorithm. | ||||
* | Merge 0.11->trunk | Kim Alvefur | 2020-03-11 | 1 | -1/+5 |
|\ | |||||
| * | mod_mam,mod_muc_mam: Allow other work to be performed during archive cleanup ↵ | Kim Alvefur | 2020-03-11 | 1 | -1/+5 |
| | | | | | | | | | | | | | | | | | | | | | | (fixes #1504) This lets Prosody handle socket related work between each step in the cleanup in order to prevent the server from being completely blocked during this. An async storage backend would not need this but those are currently rare. | ||||
| * | mod_mam: Fix rebase mistake [luacheck] | Kim Alvefur | 2019-12-24 | 1 | -1/+1 |
| | | | | | | | | The 'err' was there in trunk | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2019-12-24 | 1 | -14/+57 |
|\ \ | |/ |/| | |||||
| * | mod_mam: More careful validation of MAM query form | Kim Alvefur | 2019-12-23 | 1 | -1/+9 |
| | | | | | | | | Adapted from mod_muc_mam | ||||
| * | Merge 0.11->trunk | Matthew Wild | 2019-10-03 | 1 | -0/+2 |
| |\ | |||||
| * | | plugins: Remove tostring call from logging | Kim Alvefur | 2019-07-30 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | Taken care of by loggingmanager now Mass-rewrite using lua pattern like `tostring%b()` | ||||
| * | | mod_mam: Report correct count of results for forward queries | Kim Alvefur | 2019-07-13 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | #results is only correct for backwards queries, the table is unused for forward queries. | ||||
| * | | mod_mam: Move final log message to end of query procedure | Kim Alvefur | 2019-07-11 | 1 | -3/+3 |
| | | | |||||
| * | | mod_mam: Log RSM parameters | Kim Alvefur | 2019-07-11 | 1 | -0/+3 |
| | | | | | | | | | | | | | | | Helps when trying to figure out why some queries fail, ie when paging using an archive id that doesn't exist. | ||||
| * | | mod_mam: Log query failure reason | Kim Alvefur | 2019-07-11 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | The storage engine will usually make a lot of noise for serious errors, but not always. | ||||
| * | | mod_mam: Log more details in final log message | Kim Alvefur | 2019-07-11 | 1 | -1/+1 |
| | | | | | | | | | | | | Saves you from counting messages sent | ||||
| * | | mod_mam: Include query id in final log message | Kim Alvefur | 2019-07-11 | 1 | -1/+1 |
| | | | | | | | | | | | | Should make it easier to find related log messages | ||||
| * | | mod_mam: Use stanza id in log message as fallback if no query id | Kim Alvefur | 2019-07-11 | 1 | -1/+1 |
| | | | |||||
| * | | mod_mam: Include username that performed query | Kim Alvefur | 2019-07-11 | 1 | -1/+2 |
| | | | | | | | | | | | | Not always easy to find from surrounding logs | ||||
| * | | mod_mam: Make log message more compact | Kim Alvefur | 2019-07-11 | 1 | -4/+5 |
| | | | |||||
| * | | Merge 0.11->trunk | Kim Alvefur | 2019-05-27 | 1 | -2/+7 |
| |\ \ | |||||
| * | | | mod_mam: Propagate item-not-found to client (fixes #1325) | Kim Alvefur | 2019-05-05 | 1 | -1/+5 |
| | | | | |||||
| * | | | mod_mam: On quota hit, separately delete by time and by item count | Kim Alvefur | 2019-03-22 | 1 | -3/+11 |
| | | | | | | | | | | | | | | | | | | | | This is to work around a possible SQL issue where offsets and time stamps don't interact correctly. | ||||
| * | | | mod_mam: Trim archive when quota has been exceeded | Kim Alvefur | 2017-11-07 | 1 | -3/+18 |
| | | | | |||||
| * | | | Merge 0.11->trunk | Kim Alvefur | 2019-03-22 | 1 | -1/+1 |
| |\ \ \ | |||||
| * | | | | mod_mam: Fix operator precedence (thanks mimi89999) | Kim Alvefur | 2019-01-20 | 1 | -1/+1 |
| | | | | | |||||
| * | | | | mod_mam: Handle expiry of messages that expire in the middle of the cut-off day | Kim Alvefur | 2019-01-06 | 1 | -2/+6 |
| | | | | | |||||
| * | | | | mod_mam: Measure how long it takes to run the message expiry job job | Kim Alvefur | 2019-01-06 | 1 | -0/+3 |
| | | | | | |||||
| * | | | | mod_mam: Fix word order in log message | Kim Alvefur | 2019-01-04 | 1 | -1/+1 |
| | | | | | |||||
| * | | | | mod_mam: Perform message expiry based on building an index by date | Kim Alvefur | 2019-01-03 | 1 | -31/+39 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For each day, store a set of users that have new messages. To expire messages, we collect the union of sets of users from dates that fall outside the cleanup range. The previous algoritm did not work well with many users, especially with the default settings. | ||||
* | | | | | mod_mam: Schedule cleanup again if unable to delete messages | Kim Alvefur | 2019-12-24 | 1 | -0/+1 |
| | | | | | |||||
* | | | | | mod_mam: Log error when unable to delete old messages (fix #1479) [luacheck] | Kim Alvefur | 2019-12-24 | 1 | -0/+2 |
| | | | | | |||||
* | | | | | mod_mam: Log error when unable to store stanza (fix #1478) | Kim Alvefur | 2019-12-23 | 1 | -0/+2 |
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | | Unclear what else to do here. Caught by luacheck | ||||
* | | | | mod_mam: Add flag to session when it performs a MAM query | Matthew Wild | 2019-10-03 | 1 | -0/+2 |
| |_|/ |/| | | |||||
* | | | mod_mam: Cache last date that archive owner has messages to reduce writes ↵ | Kim Alvefur | 2019-05-27 | 1 | -1/+7 |
| |/ |/| | | | | | (fixes #1368) | ||||
* | | mod_mam: Perform message expiry based on building an index by date (backport ↵ | Kim Alvefur | 2019-03-22 | 1 | -31/+43 |
|/ | | | | | | | | | | | of 39ee70fbb009 from trunk) For each day, store a set of users that have new messages. To expire messages, we collect the union of sets of users from dates that fall outside the cleanup range. The previous algoritm did not work well with many users, especially with the default settings. | ||||
* | mod_mam: Remove embedded fallback archive driver (fixes #972) | Kim Alvefur | 2018-10-25 | 1 | -1/+0 |
| | | | | It was equivalent to mod_storage_memory, which is included as a separate module now. | ||||
* | mod_mam: Upgrade case of invalid archive store driver to hard error | Kim Alvefur | 2018-10-25 | 1 | -5/+2 |
| | |||||
* | mod_mam: Ignore case of null storage driver | Kim Alvefur | 2018-10-25 | 1 | -7/+3 |
| | |||||
* | mod_mam: Add coment on how 'complete' works | Kim Alvefur | 2018-06-10 | 1 | -0/+2 |
| | |||||
* | mod_mam: Handle edge-case of max=0 so that complete attr is set (fixes #1128) | Kim Alvefur | 2018-06-09 | 1 | -1/+1 |
| | |||||
* | mod_mam: Remove unmatched closing paren | Kim Alvefur | 2018-03-09 | 1 | -1/+1 |
| | |||||
* | mod_mam: Add an option for whether to include 'total' counts by default in ↵ | Kim Alvefur | 2018-03-07 | 1 | -2/+2 |
| | | | | queries | ||||
* | mod_mam: Log a debug message if archive expiry has been disabled | Kim Alvefur | 2018-03-07 | 1 | -0/+1 |
| | |||||
* | Backed out changeset 97a094fdf101, interferes with 6ddddfe05a74 | Kim Alvefur | 2018-03-07 | 1 | -3/+1 |
| | |||||
* | mod_mam: Implement option to enable MAM implicitly when client support is ↵ | Kim Alvefur | 2018-02-21 | 1 | -1/+3 |
| | | | | detected (#867) |