- 20 4月, 2017 3 次提交
-
-
由 Mark Haines 提交于
-
由 Kegsay 提交于
-
由 Kegsay 提交于
-
- 19 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
This has the following known shortcomings: - It doesn't handle missing events not in the from/to range. - It doesn't order events in the timeline correctly. - It doesn't handle invited/left rooms at all. - There is no intelligent wakeup logic: events for Bob will wake up Alice's stream.
-
- 18 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
Also ensure every sync response has a `next_batch` token by forcing it in the constructor, as previously timeouts would not have a token.
-
- 13 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 12 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 11 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 10 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 07 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 05 4月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 30 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 29 3月, 2017 2 次提交
- 27 3月, 2017 2 次提交
-
-
由 Kegan Dougal 提交于
-
由 Kegsay 提交于
-
- 23 3月, 2017 2 次提交
-
-
由 Mark Haines 提交于
-
由 Kegsay 提交于
Currently the HTTP handlers are attached to an API mux which is created inside Setup(). In the future, we'll want to split this out so a single mux can have both sync and clientapi handlers attached to it.
-
- 22 3月, 2017 2 次提交
- 21 3月, 2017 1 次提交
-
-
由 Mark Haines 提交于
-
- 18 3月, 2017 2 次提交
-
-
由 Kegsay 提交于
* Update gomatrixserverib dep * Use helper functions when creating rooms * Use gomatrixserverlib.StateKeyTuple
-
由 Mark Haines 提交于
-
- 17 3月, 2017 3 次提交
-
-
由 Mark Haines 提交于
-
由 Mark Haines 提交于
* Add option to stop processing input after a given number of messages
-
由 Kegsay 提交于
-
- 15 3月, 2017 4 次提交
-
-
由 Mark Haines 提交于
* Implement state conflict resolution
-
由 Kegsay 提交于
-
由 Kegsay 提交于
This involves: - Parsing the HTTP request - Requesting auth events from the roomserver via the Query API - Building the event - Doing auth checks on the event - Sending it to the roomserver input log
-
由 Mark Haines 提交于
* Tool for creating room events
-
- 13 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 11 3月, 2017 3 次提交
-
-
由 Kegsay 提交于
-
由 Kegsay 提交于
Previously, the error responses: - were not valid matrix errors (no `errcode`) - returned the `err.Error()` message which may contain sensitive information. - did not get logged (at all, let alone set the level correctly). Now the error responses: - return valid matrix errors (`M_UNKNOWN`) - return a generic "Internal Server Error" string - get logged at `ERROR` level.
-
由 Kegsay 提交于
-
- 10 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 09 3月, 2017 2 次提交
-
-
由 Mark Haines 提交于
* Return the requested portions of current state in the query API * Use Unique from github.com/matrix-org/util * rewrite bulkSelectFilteredStateBlockEntries to use append for clarity * Add test for stateKeyTupleSorter * Replace current with a new StateEntryList rather than individually setting the fields
-
由 Kegsay 提交于
-
- 08 3月, 2017 3 次提交
-
-
由 Mark Haines 提交于
This should: 1) Make the input package a bit cleaner. 2) Allow use to reuse the state reading code from the query package.
-
由 Mark Haines 提交于
* Update github.com/matrix-org/util * Use Unique from github.com/matrix-org/util
-
由 Kegsay 提交于
-