- 26 10月, 2017 1 次提交
-
-
由 Erik Johnston 提交于
This has two benefits: 1. Using channels makes it easier to time out while waiting 2. Allows us to clean up goroutines that were waiting if we timeout the request
-
- 16 10月, 2017 1 次提交
-
-
由 Erik Johnston 提交于
Including: - Handle timeout=0 correctly - Always return immediately on initial sync - Handle spurious wake ups from the notifier
-
- 13 10月, 2017 1 次提交
-
-
由 Erik Johnston 提交于
-
- 18 9月, 2017 1 次提交
-
-
由 Mark Haines 提交于
-
- 07 9月, 2017 1 次提交
-
-
由 Erik Johnston 提交于
* Turn on 'unparam' linting * Increase deadline * Fix mediaapi integeration test
-
- 06 9月, 2017 1 次提交
-
-
由 Erik Johnston 提交于
* Remove unused struct field * Ignore unused test data * Remove unused variables * Remove deadcode * Fix up vetshadow warnings * Convert to using gometalinter * Update travis * Use vendored versions of gometalinter * Make gometalinter install its stuff * Vendor misspell
-
- 22 8月, 2017 1 次提交
-
-
由 Brendan Abolivier 提交于
* Use BuildEvent method on room join * Fix building the list of room members in the sync notifier * Fix building the list of room members in the sync notifier * Rephrase comment
-
- 02 8月, 2017 1 次提交
-
-
由 Brendan Abolivier 提交于
* Clean roomserver consumer * Make account data sync incremental * Use a different name for the sync AD table * Improved error logging * Created missing topic in tests * Add client API topic to tests * Add client API topic to common * Move data batch retrieval * Add database index for data retrieval * Fix typo in table name * Fix indentation
-
- 07 7月, 2017 1 次提交
-
-
由 Mark Haines 提交于
* Use utility methods from gomatrixserverlib, rather than reimplementing them * Return string rather than pointer to string * Update gomatrixserverlib
-
- 18 5月, 2017 1 次提交
-
-
由 Kegsay 提交于
- `s/Server/OutputRoomEvent/` in `consumers` to accurately reflect what is being consumed. - `s/set/userIDSet/` in `notifier.go` for clarity. - Removed lying comments.
-
- 17 5月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 10 5月, 2017 1 次提交
-
-
由 Kegsay 提交于
* Split out notifying /sync requests and calculating sync responses The logic for notifying /sync requests is about to get really complicated as we optimise when to wake up requests, so split out that code into a separate struct to isolate it and make it easier to unit test.
-