anonymousland-synapse/stubs/sortedcontainers/__init__.pyi

from .sorteddict import SortedDict, SortedItemsView, SortedKeysView, SortedValuesView
from .sortedlist import SortedKeyList, SortedList, SortedListWithKey
from .sortedset import SortedSet

__all__ = [
    "SortedDict",
    "SortedKeysView",
    "SortedItemsView",
    "SortedValuesView",
    "SortedKeyList",
    "SortedList",
    "SortedListWithKey",
    "SortedSet",
]
Enable mypy for synapse.util.caches (#8547) This seemed to entail dragging in a type stub for SortedList. 2020-10-15 06:44:39 -04:00			`from .sorteddict import SortedDict, SortedItemsView, SortedKeysView, SortedValuesView`
			`from .sortedlist import SortedKeyList, SortedList, SortedListWithKey`
Speed up MultiWriterIdGenerator when lots of IDs are in flight. (#10755) 2021-09-03 13:23:46 -04:00			`from .sortedset import SortedSet`
Extend StreamChangeCache to support multiple entities per stream ID (#7303) First some background: StreamChangeCache is used to keep track of what "entities" have changed since a given stream ID. So for example, we might use it to keep track of when the last to-device message for a given user was received [1], and hence whether we need to pull any to-device messages from the database on a sync [2]. Now, it turns out that StreamChangeCache didn't support more than one thing being changed at a given stream_id (this was part of the problem with #7206). However, it's entirely valid to send to-device messages to more than one user at a time. As it turns out, this did in fact work, because some methods of StreamChangeCache coped ok with having multiple things changing on the same stream ID, and it seems we never actually use the methods which don't work on the stream change caches where we allow multiple changes at the same stream ID. But that feels horribly fragile, hence: let's update StreamChangeCache to properly support this, and add some typing and some more tests while we're at it. [1]: https://github.com/matrix-org/synapse/blob/release-v1.12.3/synapse/storage/data_stores/main/deviceinbox.py#L301 [2]: https://github.com/matrix-org/synapse/blob/release-v1.12.3/synapse/storage/data_stores/main/deviceinbox.py#L47-L51 2020-04-22 08:45:40 -04:00
			`__all__ = [`
			`"SortedDict",`
			`"SortedKeysView",`
			`"SortedItemsView",`
			`"SortedValuesView",`
Enable mypy for synapse.util.caches (#8547) This seemed to entail dragging in a type stub for SortedList. 2020-10-15 06:44:39 -04:00			`"SortedKeyList",`
			`"SortedList",`
			`"SortedListWithKey",`
Speed up MultiWriterIdGenerator when lots of IDs are in flight. (#10755) 2021-09-03 13:23:46 -04:00			`"SortedSet",`
Extend StreamChangeCache to support multiple entities per stream ID (#7303) First some background: StreamChangeCache is used to keep track of what "entities" have changed since a given stream ID. So for example, we might use it to keep track of when the last to-device message for a given user was received [1], and hence whether we need to pull any to-device messages from the database on a sync [2]. Now, it turns out that StreamChangeCache didn't support more than one thing being changed at a given stream_id (this was part of the problem with #7206). However, it's entirely valid to send to-device messages to more than one user at a time. As it turns out, this did in fact work, because some methods of StreamChangeCache coped ok with having multiple things changing on the same stream ID, and it seems we never actually use the methods which don't work on the stream change caches where we allow multiple changes at the same stream ID. But that feels horribly fragile, hence: let's update StreamChangeCache to properly support this, and add some typing and some more tests while we're at it. [1]: https://github.com/matrix-org/synapse/blob/release-v1.12.3/synapse/storage/data_stores/main/deviceinbox.py#L301 [2]: https://github.com/matrix-org/synapse/blob/release-v1.12.3/synapse/storage/data_stores/main/deviceinbox.py#L47-L51 2020-04-22 08:45:40 -04:00			`]`