Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Maunium
synapse
Commits
91f8de7b
Unverified
Commit
91f8de7b
authored
2 years ago
by
Andrew Morgan
Committed by
GitHub
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Clarify the workers that the ThirdPartyRules' `on_new_event` callback will run on (#15071)
parent
647ff3ef
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
changelog.d/15071.doc
+1
-0
1 addition, 0 deletions
changelog.d/15071.doc
docs/modules/third_party_rules_callbacks.md
+3
-0
3 additions, 0 deletions
docs/modules/third_party_rules_callbacks.md
with
4 additions
and
0 deletions
changelog.d/15071.doc
0 → 100644
+
1
−
0
View file @
91f8de7b
Clarify which worker processes the ThirdPartyRules' [`on_new_event`](https://matrix-org.github.io/synapse/v1.78/modules/third_party_rules_callbacks.html#on_new_event) module API callback runs on.
\ No newline at end of file
This diff is collapsed.
Click to expand it.
docs/modules/third_party_rules_callbacks.md
+
3
−
0
View file @
91f8de7b
...
@@ -146,6 +146,9 @@ Note that this callback is called when the event has already been processed and
...
@@ -146,6 +146,9 @@ Note that this callback is called when the event has already been processed and
into the room, which means this callback cannot be used to deny persisting the event. To
into the room, which means this callback cannot be used to deny persisting the event. To
deny an incoming event, see
[
`check_event_for_spam`
](
spam_checker_callbacks.md#check_event_for_spam
)
instead.
deny an incoming event, see
[
`check_event_for_spam`
](
spam_checker_callbacks.md#check_event_for_spam
)
instead.
For any given event, this callback will be called on every worker process, even if that worker will not end up
acting on that event. This callback will not be called for events that are marked as rejected.
If multiple modules implement this callback, Synapse runs them all in order.
If multiple modules implement this callback, Synapse runs them all in order.
### `check_can_shutdown_room`
### `check_can_shutdown_room`
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment