|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | |  | 
| | 
| 
| 
| 
| 
| 
| | Part of #9744
Removes all redundant `# -*- coding: utf-8 -*-` lines from files, as python 3 automatically reads source code as utf-8 now.
`Signed-off-by: Jonathan de Jong <jonathan@automatia.nl>` | 
| | 
| 
| | The idea is that in future tokens will encode a mapping of instance to position. However, we don't want to include the full instance name in the string representation, so instead we'll have a mapping between instance name and an immutable integer ID in the DB that we can use instead. We'll then do the lookup when we serialize/deserialize the token (we could alternatively pass around an `Instance` type that includes both the name and ID, but that turns out to be a lot more invasive). | 
| | 
| 
| 
| 
| 
| 
| | This converts calls like super(Foo, self) -> super().
Generated with:
    sed -i "" -Ee 's/super\([^\(]+\)/super()/g' **/*.py | 
| | |  | 
| | 
| 
| 
| 
| | Python will return a tuple whether there are parentheses around the returned values or not.
I'm just sick of my editor complaining about this all over the place :) | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| | parse_integer and parse_string can take a request and raise errors
in case we have wrong or missing params.
This PR tries to use them more to deduplicate some code and make it
better readable | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| | hs.get_handlers() can not be invoked from split out processes. Moving
the invocations down a level means that we can slowly split out
individual servlets. | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | This tracks data about the entity which made the request. This is
instead of passing around a tuple, which requires call-site
modifications every time a new piece of optional context is passed
around.
I tried to introduce a User object. I gave up. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| | This follows the same flows-based flow as regular registration, but as
the only implemented flow has no requirements, it auto-succeeds. In the
future, other flows (e.g. captcha) may be required, so clients should
treat this like the regular registration flow choices. | 
| | |  | 
| | |  | 
| | 
| 
| 
| | Client-Server API | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| | Removes device_id and ClientInfo
device_id is never actually written, and the matrix.org DB has no
non-null entries for it. Right now, it's just cluttering up code.
This doesn't remove the columns from the database, because that's
fiddly. | 
| | 
| 
| 
| | device_id in the internal meta data for the event along with the transaction id when sending events | 
| | |  | 
| | |  | 
|  |  |