| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
Add some comments about the reactor tick time metric
|
| | | |
|
| | |
| |
| | |
blindly implement ?ts for AS. untested
|
| | |
| |
| |
| |
| |
| | |
Add federation_domain_whitelist
gives a way to restrict which domains your HS is allowed to federate with.
useful mainly for gracefully preventing a private but internet-connected HS from trying to federate to the wider public Matrix network
|
| |\ \
| |/
|/| |
add registrations_require_3pid and allow_local_3pids
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
* [ ] split config options into allowed_local_3pids and registrations_require_3pid
* [ ] simplify and comment logic for picking registration flows
* [ ] fix docstring and move check_3pid_allowed into a new util module
* [ ] use check_3pid_allowed everywhere
@erikjohnston PTAL
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
lets homeservers specify a whitelist for 3PIDs that users are allowed to associate with.
Typically useful for stopping people from registering with non-work emails
|
| |\ \
| | |
| | | |
Use the right path for url_preview thumbnails
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was introduced by #2627: we were overwriting the original media for url
previews with the thumbnails :/
(fixes https://github.com/vector-im/riot-web/issues/6012, hopefully)
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Make storage providers configurable
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Add decent impl of a FileConsumer
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Twisted core doesn't have a general purpose one, so we need to write one
ourselves.
Features:
- All writing happens in background thread
- Supports both push and pull producers
- Push producers get paused if the consumer falls behind
|
| | |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
... which I introduced in #2785
|
| |\ \ \
| |_|/
|/| | |
better exception logging in callbackmetrics
|
| | | |
| | |
| | |
| | | |
when we fail to render a metric, give a clue as to which metric it was
|
| |\ \ \
| |/ /
|/| | |
Log room when doing state resolution
|
| | | |
| | |
| | |
| | | |
Mostly because it helps figure out what is prompting the resolution
|
| |\ \ \
| | | |
| | | | |
Keep track of last access time for local media
|
| | | | | |
|
| | | | | |
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | | |
fix SQL when searching all users
|
| | | | | |
|
| |/ / /
| | |
| | |
| | | |
... so that the return type doesn't depend on the arg types
|
| |\ \ \
| | | |
| | | | |
Track DB scheduling delay per-request
|
| | |\ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For each request, track the amount of time spent waiting for a db
connection. This entails adding it to the LoggingContext and we may as well add
metrics for it while we are passing.
|
| | |\ \ \ \ |
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Sanity checking for user ids
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Check the user_id passed to a couple of APIs for validity, to avoid
"IndexError: list index out of range" exception which looks scary and results
in a 500 rather than a more useful error.
Fixes #1432, among other things
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Track db txn time in millisecs
|
| | |\| | | | |
| | |_|/ / /
| |/| | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
... to reduce the amount of floating-point foo we do.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix 'NoneType' object has no attribute 'writeHeaders'
|
| | |\ \ \ \ \ \
| | | |/ / / /
| | |/| | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Avoid throwing a (harmless) exception when we try to write an error response to
an http request where the client has disconnected.
This comes up as a CRITICAL error in the logs which tends to mislead people
into thinking there's an actual problem
|
| |\ \ \ \ \ \ \
| | |/ / / / /
| |/| | / / /
| |_|_|/ / /
|/| | | | | |
|
| | |\ \ \ \ \
| | |_|/ / /
| |/| | / /
| | | |/ /
| | |/| | |
|
| | | |\ \ \
| | | | | |
| | | | | | |
Fix thumbnailing remote files
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | |/ /
| | |/| | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It turns out that the only thing we use the __dict__ of LoggingContext for is
`request`, and given we create lots of LoggingContexts and then copy them every
time we do a db transaction or log line, using the __dict__ seems a bit
redundant. Let's try to optimise things by making the request attribute
explicit.
|
| |/ / /
| | |
| | |
| | | |
... so that we can share the code
|
| |\ \ \
| | | |
| | | | |
Reorganise request and block metrics
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In order to circumvent the number of duplicate foo:count metrics increasing
without bounds, it's time for a rearrangement.
The following are all deprecated, and replaced with synapse_util_metrics_block_count:
synapse_util_metrics_block_timer:count
synapse_util_metrics_block_ru_utime:count
synapse_util_metrics_block_ru_stime:count
synapse_util_metrics_block_db_txn_count:count
synapse_util_metrics_block_db_txn_duration:count
The following are all deprecated, and replaced with synapse_http_server_response_count:
synapse_http_server_requests
synapse_http_server_response_time:count
synapse_http_server_response_ru_utime:count
synapse_http_server_response_ru_stime:count
synapse_http_server_response_db_txn_count:count
synapse_http_server_response_db_txn_duration:count
The following are renamed (the old metrics are kept for now, but deprecated):
synapse_util_metrics_block_timer:total ->
synapse_util_metrics_block_time_seconds
synapse_util_metrics_block_ru_utime:total ->
synapse_util_metrics_block_ru_utime_seconds
synapse_util_metrics_block_ru_stime:total ->
synapse_util_metrics_block_ru_stime_seconds
synapse_util_metrics_block_db_txn_count:total ->
synapse_util_metrics_block_db_txn_count
synapse_util_metrics_block_db_txn_duration:total ->
synapse_util_metrics_block_db_txn_duration_seconds
synapse_http_server_response_time:total ->
synapse_http_server_response_time_seconds
synapse_http_server_response_ru_utime:total ->
synapse_http_server_response_ru_utime_seconds
synapse_http_server_response_ru_stime:total ->
synapse_http_server_response_ru_stime_seconds
synapse_http_server_response_db_txn_count:total ->
synapse_http_server_response_db_txn_count
synapse_http_server_response_db_txn_duration:total
synapse_http_server_response_db_txn_duration_seconds
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Fix a logcontext leak in persist_events
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ObserveableDeferred expects its callbacks to be called without any
logcontexts, whereas it turns out we were calling them with the logcontext of
the request which initiated the persistence loop.
It seems wrong that we are attributing work done in the persistence loop to the
request that happened to initiate it, so let's solve this by dropping the
logcontext for it.
(I'm not sure this actually causes any real problems other than messages in the
debug log, but let's clean it up anyway)
|
| |\ \ \ \
| | | | |
| | | | | |
Metrics for events processed in appservice and fed sender
|
| | |/ / /
| | | |
| | | |
| | | | |
More metrics I wished I'd had
|
| |\ \ \ \
| |_|/ /
|/| | | |
Metrics for number of RDATA commands received
|
| | |/ /
| | |
| | |
| | | |
I found myself wishing we had this.
|
| |\ \ \
| |/ /
|/| | |
Refactor MediaRepository to separate out storage
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |\ \
| | | |
| | | |
| | | | |
erikj/media_storage_refactor
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
Prometheus handles all metrics as floats, and sometimes we store non-integer
values in them (notably, durations in seconds), so let's render them as floats
too.
(Note that the standard client libraries also treat Counters as floats.)
|
| | | |
| | |
| | |
| | |
| | | |
We need to actually download the remote media when we get a request for a
thumbnail.
|
| |\ \ \
| |_|/
|/| | |
When using synctl with workers, don't start the main synapse automatically
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
Add /room/{id}/event/{id} to synapse
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Turns out that there is a valid usecase for retrieving event by id (notably
having received a push), but event ids should be scoped to room, so /event/{id}
is wrong.
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Do bcrypt hashing in a background thread
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
which was missing its fed client API, since there is no other API
it might as well reuse the bulk one and unwrap it
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
Update http request metrics before calling servlet
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
Make sure that we set the servlet name in the metrics object *before* calling
the servlet, in case the servlet throws an exception.
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
Fix broken config UTs
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
https://github.com/matrix-org/synapse/pull/2755 broke log-config generation,
which in turn broke the unit tests.
|
| |/ / /
| | |
| | |
| | | |
(we had a mix of 2- and 4-space indents)
|
| | | |
| | |
| | |
| | |
| | | |
Fixes https://github.com/matrix-org/synapse/issues/2759
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
... because these only really exist to confuse people nowadays.
Also bring log config more into line with the generated log config, by making `level_for_storage`
apply to the `synapse.storage.SQL` logger rather than `synapse.storage`.
|
| |\ \ \
| | | |
| | | | |
Better logging when login can't find a 3pid
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Return a 400 rather than a 500 when somebody messes up their send_join
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
turns out we have two copies of this, and neither needs to be an instance
method
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
synapse/config/password_auth_providers: Fixed bracket typo
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Richard von Seck <richard.von-seck@gmx.net>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Silke <silke@slxh.eu>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Silke <silke@slxh.eu>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add listen_tcp and listen_ssl which implement Twisted's reactor.listenTCP
and reactor.listenSSL for multiple addresses.
Signed-off-by: Silke Hofstra <silke@slxh.eu>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Binding on 0.0.0.0 when :: is specified in the bind_addresses is now allowed.
This causes a warning explaining the behaviour.
Configuration changed to match.
See #2232
Signed-off-by: Silke Hofstra <silke@slxh.eu>
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Most deployments are on Linux (or Mac OS), so this would actually bind
on both IPv4 and IPv6.
Resolves #1886.
Signed-off-by: Willem Mulder <willemmaster@hotmail.com>
|
| |\ \ \
| | | |
| | | |
| | | | |
erikj/createroom_content
|
| | |\ \ \
| | | | |
| | | | | |
Add all local users to the user_directory and optionally search them
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | |\ \ \
| | | | |/
| | | |/| |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
additional users
Initial commit; this doesn't work yet - the LIKE filtering seems too aggressive.
It also needs _do_initial_spam to be aware of prepopulating the whole user_directory_search table with all users...
...and it needs a handle_user_signup() or something to be added so that new signups get incrementally added to the table too.
Committing it here as a WIP
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This was introduced in d7ea8c4 / PR #2728
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Wire the custom login type support from password providers into the UI-auth
user-validation flows.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Collect together all the places that validate a logged-in user via UI auth.
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | | |
Instead of returning False when auth is incomplete, throw an exception which
can be caught with a wrapper.
|
| | |\ \ \
| | | | |
| | | | | |
Improve comments on get_user_by_access_token
|
| | | | | |
| | | | |
| | | | |
| | | | | |
because I have to reverse-engineer this every time.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make sure that we delete devices whenever a user is logged out due to any of
the following situations:
* /logout
* /logout_all
* change password
* deactivate account (by the user or by an admin)
* invalidate access token from a dynamic module
Fixes #2672.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Non-functional refactoring to move set_password. This means that we'll be able
to properly deactivate devices and access tokens without introducing a
dependency loop.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Non-functional refactoring to move deactivate_account. This means that we'll be
able to properly deactivate devices and access tokens without introducing a
dependency loop.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Whenever an access token is invalidated, we should remove the associated
pushers.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Clear logcontext before starting fed txn queue runner
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | | |
These processes take a long time compared to the request, so there is lots of
"Entering|Restoring dead context" in the logs. Let's try to shut it up a bit.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Fix 500 when joining matrix-dev
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
matrix-dev has an event (`$/6ANj/9QWQyd71N6DpRQPf+SDUu11+HVMeKSpMzBCwM:zemos.net`)
which has no `hashes` member.
Check for missing `hashes` element in events.
|
| | |/ / / |
|
| | |\ \ \
| | | | |
| | | | | |
Fix error on sqlite 3.7
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
so that the right thing happens on workers.
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Create the url_cache index on local_media_repository as a background update, so
that we can detect whether we are on sqlite or not and create a partial or
complete index accordingly.
To avoid running the cleanup job before we have built the index, add a bailout
which will defer the cleanup if the bg updates are still running.
Fixes https://github.com/matrix-org/synapse/issues/2572.
|
| | |\ \ \
| | | | |
| | | | | |
Avoid retrying forever on IntegrityError
|
| | | | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Fix error handling on dns lookup
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
pass the right arguments to the errback handler
Fixes "TypeError('eb() takes exactly 2 arguments (1 given)',)"
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Tiny code cleanups
|
| | | | | | | |
|
| | | |/ / /
| | | | |
| | | | |
| | | | | |
This is never used; let's remove it to stop confusing things.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Fix some logcontext leaks in replication resource
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | | |
The @measure_func annotations rely on the wrapped function respecting the
logcontext rules. Add the necessary yields to make this work.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Fix OPTIONS on preview_url
|
| | | |/ / /
| | | | |
| | | | |
| | | | | |
Fixes #2706
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
Use failure.Failure to recover our failure, which will give us a useful
stacktrace, unlike the rethrown exception.
|
| | | | |
| | | |
| | | |
| | | | |
... to stop us doing the cache cleanup jobs on the master.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This avoids the scenario where we have four different PreviewUrlResources
configured on a single app, each of which have their own caches and cache
clearing jobs.
|
| | |\ \ \
| | | | |
| | | | | |
Clean up dependency list
|
| | | |/ /
| | | |
| | | |
| | | |
| | | | |
remove those that aren't used at all, and replace the ones that don't have
builders with simple getters rather than dynamically-generated methods.
|
| | |\ \ \
| | |/ /
| |/| | |
Avoid locking account_data tables for upserts
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
Avoid locking for upsert on pushers tables
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* replace the upsert into deleted_pushers with an insert
* no need to lock for upsert on pusher_throttle
|
| | |\ \ \ \ |
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | | |
Add automagical AS Publicised Group(s)
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | |_|_|/
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
via registration file "users" namespace:
```YAML
...
namespaces:
users:
- exclusive: true
regex: '.*luke.*'
group_id: '+all_the_lukes:hsdomain'
...
```
This is part of giving App Services their own groups for matching users. With this, ghost users will be given the appeareance that they are in a group and that they have publicised the fact, but _only_ from the perspective of the `get_publicised_groups_for_user` API.
|
| | | |_|_|/
| |/| | | |
|
| | | |_|/
| |/| | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Now that _simple_upsert will retry on IntegrityError, we don't need to lock the
table.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
wrap the call to _simple_upsert_txn in a loop so that we retry on an
integrityerror: this means we can avoid locking the table provided there is an
unique index.
|
| | |/ /
| | |
| | |
| | | |
Bail out early to reduce indentation
|
| | |\ \
| | | |
| | | | |
Pull out bits of StateStore to a mixin
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... so that we don't need to secretly gut-wrench it for use in the slaved
stores. I haven't done the other stores yet, but we should. I'm tired of the
workers breaking every time we tweak the stores because I forgot to gut-wrench
the right method.
fixes https://github.com/matrix-org/synapse/issues/2655.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We're going to fix this properly on this branch, so that the _state_group_cache
can end up in StateGroupReadStore.
This reverts commit ab335edb023d66cd0be439e045b10ca104b73cb5.
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
Remove preserve_context_over_{fn, deferred}
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Both of these functions ae known to leak logcontexts. Replace the remaining
calls to them and kill them off.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Rename redact_content option to include_content
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
because we had to wait until the logger was set up
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The redact_content option never worked because it read the wrong config
section. The PR introducing it
(https://github.com/matrix-org/synapse/pull/2301) had feedback suggesting the
name be changed to not re-use the term 'redact' but this wasn't
incorporated.
This reanmes the option to give it a less confusing name, and also
means that people who've set the redact_content option won't suddenly
see a behaviour change when upgrading synapse, but instead can set
include_content if they want to.
This PR also updates the wording of the config comment to clarify
that this has no effect on event_id_only push.
Includes https://github.com/matrix-org/synapse/pull/2422
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | | |
Reshuffle room list request code
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
I'm not entirely sure if this will actually help anything, but it simplifies
the code and might give further clues about why room list search requests are
blowing out the get_current_state_ids caches.
|
| | | | |/ / /
| | |/| | |
| | | | | |
| | | | | | |
So we can see what it gets up to.
|
| | | | | | | |
|
| | | | | | | |
|
| | |_|_|_|/
|/| | | |
| | | | | |
We reused the `content` dictionary between invite requests, which meant they could end up reusing the profile info for a previous user
|
| | | | | | |
|
| |/ / / / |
|
| | |_|/
|/| | |
|
| |\ \ \
| |/ /
|/| | |
Make __init__ consistent across Store hierarchy
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Add db_conn parameters to the `__init__` methods of the *Store classes, so that
they are all consistent, which makes the multiple inheritance work correctly
(and so that we can later extract mixins which can be used in the slavedstores)
|
| |\ \ \
| | | |
| | | | |
Add a route for determining who you are
|
| | | | |
| | | |
| | | | |
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Useful for applications which may have an access token, but no idea as to who owns it.
Signed-off-by: Travis Ralston <travpc@gmail.com>
|
| |\ \ \ \
| | | | |
| | | | | |
Cache failures in url_preview handler
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
Reshuffle the caching logic in the url_preview handler so that failures are
cached (and to generally simplify things and fix the logcontext leaks).
|
| |\ \ \ \
| | |/ /
| |/| | |
|
| | | | |
| | | |
| | | |
| | | | |
This reverts commit f5cf3638e9c6086e1c33ddad8eda9298cf53a58e.
|
| | |/ / |
|
| | | |
| | |
| | |
| | | |
Explain why we don't validate userids registered via app services
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Force username to lowercase before attempting to register
https://github.com/matrix-org/synapse/issues/2660
|
| | | |
| | |
| | |
| | | |
This reverts commit b70b64690330c25cbd04c1b2cacf8276b566efc8.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
If somebody sends us a request where the the body is invalid utf-8, we should
return a 400 rather than a 500. (json.loads throws a UnicodeError in this
situation)
We might as well catch all Exceptions here: it seems very unlikely that we
would get a request that *isn't caused by invalid json.
|
| | |
| |
| |
| | |
Because we're never going to be able to fix this :'(
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Fix 'NoneType' not iterable in /deactivate
|
