Johannes Becker

Personally I'd say the solution proposed in #92 would fit nicely here. I'm also having that use case where I have multiple endpoints that are exclusively used in tests, such...

Instead of making it a breaking change it could also be an opt-in option, maybe when creating the server url. I've just run into cases where I forgot to assert...

@MTRNord This should be fixed in https://github.com/matrix-org/matrix-rust-sdk/pull/254 which also includes a bugfix due to improved test coverage. The issue being that identity assertion and auth forcing didn't work as expected...

@MTRNord Also, about `invite` vs `join` events, please see https://docs.ruma.io/ruma/api/appservice/event/push_events/v1/struct.IncomingRequest.html#method.try_into_sync_response for the rationale. Added that text to the `set_event_handler` docs as well now. Hope that makes sense. If you have...

@agraven Clarified that item's description. The linked PR was only about introducing it on the `Client`, I think it needs more work to support it in the appservice crate

Clarification: This is about logs for the tracing `TRACE` level

Thought on implementation details: Maybe this could be solved in the store? Basically: `.send` already creates an entry in the store but marks it as "not synced" and waits for...

It's also an usability horror to not know which state the SDK is in after calling high level APIs. I wonder whether there's a way to solve this in a...

Generally regarding deadlocks: In some cases this doesn't seem avoidable and is something consumers just need to be aware of and know how to handle them. Examples would be locks...

The mentioned APIs were meant as an example that it's rather common in the rust ecosystem to expose potential deadlocks in the public API, since even the std library is...