aboutsummaryrefslogtreecommitdiffstats
path: root/plugins
Commit message (Collapse)AuthorAgeFilesLines
...
* | mod_smacks: Split log messages for when an old session exists in storageKim Alvefur2021-12-171-1/+2
| | | | | | | | Non-existent did not seem entirely accurate for this case
* | mod_smacks: Bounce unacked stanzas on shutdownKim Alvefur2021-12-171-1/+11
| |
* | mod_smacks: Preserve counter values on shutdownKim Alvefur2021-12-171-0/+22
| |
* | mod_smacks: Simplify access to local user sessionsKim Alvefur2021-12-171-2/+2
| | | | | | | | | | Less to type if per chance the next commit also wants to access sessions.
* | mod_smacks: Cancel hibernation when session is closedKim Alvefur2021-12-161-0/+6
| | | | | | | | | | | | To ensure that if a session is replaced after it has gone into hibernation, it does not come back and cause trouble for the new session (see previous commit).
* | mod_smacks: Skip hibernation logic if session was closed or replacedKim Alvefur2021-12-161-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | The resumption_token is removed when the session is closed via the pre-session-close event, signaling that it cannot be resumed, and therefore no hibernation timeout logic should be invoked. Fixes that if a session somehow is replaced by a new one using the same resource (which is the common behavior), the old session would still be around until it times out at which point it sends `<presence type="unavailable"/>` which would look as if it came from the new session, ie appearing offline to everyone including MUCs.
* | mod_smacks: Fix indentationKim Alvefur2021-12-161-4/+4
| | | | | | | | Meld keeps messing up indentation when I merge and rebase...
* | mod_smacks: Stop stanzas from being queued on hibernation timeoutKim Alvefur2021-12-161-0/+1
| | | | | | | | | | | | | | | | | | | | This overloads that flag a bit, but it has the intended effect of stopping outgoing_stanza_filter() from queueing stanzas. Fixes a traceback because of the queue having been removed somewhere around here, since it is no longer needed. Thanks Martin for reporting
* | mod_smacks: Limit queue memory consumption using new utilKim Alvefur2021-12-142-52/+73
| | | | | | | | | | | | | | | | | | This brings back the queue size limit that was once added, then removed because destroying the session when reaching the limit was not great. Instead, the queue wraps and overwrites the oldest unacked stanza on the assumption that it will probably be acked anyway and thus does not need to be delivered. If those discarded stanzas turn out to be needed on resumption then the resumption fails.
* | mod_smacks: Set a watchdog to watch sleeping sessionsKim Alvefur2021-12-021-59/+27
| | | | | | | | | | Extending the timeout by poking the watchdog, and letting it go on resumption, should be much better than the previous method.
* | mod_smacks: Switch storage for tracking resumption tokensKim Alvefur2021-12-021-40/+5
| | | | | | | | | | | | | | | | All that was a complicated way to limit the number of resumable sessions. Let's control resource usage some other way. This leaves the essence of mapping resumption tokens to live sessions. This keeps resumption state across reloads.
* | mod_smacks: Clear resumption token from persistent storage on resumptionKim Alvefur2021-12-011-0/+1
| |
* | mod_smacks: Persist old counter values to storageKim Alvefur2021-12-011-7/+5
| | | | | | | | | | | | | | | | | | This allows clients that try to resume a session after a server restart to at least know which of their pending outgoing stanzas were received and which need to be re-sent. This removes the limit on how many of those counters are kept, which should be fixed eventually.
* | mod_smacks: Remove now unused variable [luacheck]Kim Alvefur2021-12-151-1/+1
| |
* | mod_smacks: Remove unused eventKim Alvefur2021-12-151-1/+0
| | | | | | | | | | Since nothing uses it. Some equivalent functionality may return in the future.
* | mod_smacks: Fix typoKim Alvefur2021-12-151-1/+1
| |
* | mod_smacks: Flag both sessions to prevent duplicating queue on resumptionKim Alvefur2021-12-141-0/+3
| | | | | | | | | | | | | | I have no idea what is going on in this code, which session is which? Something has one of the sessions as an upvalue which is where the filter checks for it.
* | mod_smacks: Increment a counter for each resumptionKim Alvefur2021-12-061-0/+1
| | | | | | | | | | Encountered what looks like a bug where after *many* resumptions, part of the queue was not acked.
* | mod_smacks: Back out 48f8fa6cea7b - back in a86ae74da96c againKim Alvefur2021-12-131-2/+4
| | | | | | | | Maybe it works now with the session patching in the previous commit
* | mod_smacks: Patch various self-references on the resumed sessionKim Alvefur2021-12-131-0/+5
| | | | | | | | | | The number of places where the session is an upvalue to its own methods is too high!
* | mod_smacks: Back out a86ae74da96c: Fixed one problem, caused anotherKim Alvefur2021-12-131-4/+2
| | | | | | | | | | | | | | | | As per a86ae74da96c the 'session' object here is the wrong session, so the attempt to block stanzas from being added to the queue twice did not work causing something of a leak. Instead we have a leak of the previous session.
* | mod_smacks: Back out def20683c161Kim Alvefur2021-12-131-1/+0
| | | | | | | | The attempted fix completely broke everything after resumption.
* | mod_smacks: Update reference to session from send()Kim Alvefur2021-12-131-0/+1
| | | | | | | | | | | | a86ae74da96c caused the stanza queue to double on resumption because session.send() keeps a reference to the session which is what gets passed to filters, so the added flag was not seen in the filter.
* | mod_smacks: Include reason for destroying session on hibernation timeoutKim Alvefur2021-12-121-1/+1
| | | | | | | | To aid in debugging
* | mod_mam: Avoid storing bounces for messages from the bare account (thanks Ge0rG)Kim Alvefur2021-12-101-2/+12
| | | | | | | | | | | | This should rule out error replies to PEP notifications, which come from the account bare JID, and would be reflected back to it if they can't be delivered for some reason, e.g. s2s problems.
* | MUC: Remove <{muc}x> tags in some errorsKim Alvefur2021-12-084-6/+6
| | | | | | | | | | Including the payload of the stanza that caused the error is optional and we're generally not doing it anywhere else.
* | MUC: Fix error origin JID in wrong argument positionKim Alvefur2021-12-081-1/+1
| | | | | | | | | | Mistake introduced in cbe524ed1a6a. Removing because this is a query to the bare JID where the error origin matches the resulting stanza 'from'.
* | MUC: Remove remaining deprecated numeric error codesKim Alvefur2021-12-083-4/+0
| | | | | | | | | | | | The numeric error codes seems to have been removed from the examples in XEP-0045 version 1.24, and were deprecated even by RFC 3920 in 2004, only allowed for backwards compatibility.
* | MUC: Return a friendly textual error when trying to speak without voiceKim Alvefur2021-12-081-1/+2
| | | | | | | | | | | | I spend several minutes confused over where the bug was until I remembered I had set myself as visitor in the previous debug session. This would have helped.
* | mod_admin_shell: Add port as a c2s/s2s:show column definitionKim Alvefur2021-12-071-0/+7
| | | | | | | | | | Allows inferring whether Direct TLS was used, or perhaps which SRV record was chosen. Not shown by default.
* | mod_pep: Set correct jid attr on node disco itemsKim Alvefur2021-12-071-0/+1
| | | | | | | | | | It was previously set to the hostname, not the users bare JID which would be correct.
* | mod_pubsub: Allow specifying the JID of the pubsub serviceKim Alvefur2021-12-072-1/+2
| | | | | | | | | | This allows overriding it in cases where it is not equal to module.host, like say, in mod_pep
* | mod_admin_shell: Handle global roles (pass host=*)Kim Alvefur2021-12-061-1/+2
| | | | | | | | Is it not odd that um.set_roles() takes `nil` to mean global?
* | mod_admin_shell: Only check that local users exist locallyKim Alvefur2021-12-061-3/+1
| |
* | mod_disco: Optionally return info on admin accounts to non-contactsKim Alvefur2021-04-151-2/+5
| | | | | | | | | | If you already know the account, from say the server contact info, then this confirms their admin status.
* | mod_disco: Advertise anonymous usersKim Alvefur2020-07-041-0/+2
| | | | | | | | Can these even be seen?
* | mod_disco: Advertise admin accounts as such via disco identityKim Alvefur2020-07-041-1/+6
| |
* | mod_admin_shell: Support setting roles on hosts other than the users'Kim Alvefur2021-12-061-4/+8
| | | | | | | | | | | | | | | | Needed to e.g. grant admin rights on a component, or grant non-local users local privileges. Leave the same host syntax for convenience, since this might be the common case.
* | mod_admin_shell: Add command for updating roles user:roles(jid, roles)Kim Alvefur2021-12-061-4/+19
| | | | | | | | | | This would allow e.g. granting admin status without changing the config and without a restart.
* | mod_admin_shell: Allow setting roles when creating userKim Alvefur2021-12-041-2/+12
| |
* | MUC: Allow modules a chance to act prior to room destructionKim Alvefur2021-12-052-7/+19
| |
* | mod_cron: Expose the One Timer via module environmentKim Alvefur2021-12-041-1/+1
| | | | | | | | | | This makes it easier to reschedule or otherwise manipulate the timer from e.g. the shell, which is handy for debugging.
* | mod_http_file_share: Fix to take retention time into accountKim Alvefur2021-12-041-1/+2
| | | | | | | | It was lost in 6f4790b8deec when switching to mod_cron.
* | mod_http_file_share: Improve consistency of terminology in loggingKim Alvefur2021-12-041-8/+8
| | | | | | | | | | Prefer 'prune' over 'delete' since it more strongly implies removal of excess.
* | mod_http_file_share: Rename variable for clarityKim Alvefur2021-12-041-6/+6
| |
* | mod_http_file_share: Fix deletion counterKim Alvefur2021-12-041-4/+3
| | | | | | | | | | Before aa60f4353001 each loop had its own counter, seems incrementing of one of them was lost. But only one is needed anyhow.
* | mod_http_file_share: Back out 876e1b6d6ae4Kim Alvefur2021-12-031-2/+2
| |
* | mod_http_file_share: Recalculate total storage usage weekly instead of dailyKim Alvefur2021-12-031-1/+1
| | | | | | | | | | | | Before mod_cron this job ran less frequently than the upload removal job. Running them at the same frequency seems wasteful somehow, plus the total should not drift away from the true value that fast.
* | mod_cron: Add a 'weekly' job frequencyKim Alvefur2021-12-031-1/+1
| |
* | mod_cron: Initialize timestamp of new tasks to start of periodKim Alvefur2021-12-031-2/+2
| | | | | | | | | | Makes it more generic so new periods (e.g. weekly etc) can be added easily.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 08:00:23 +0000