forked from famedly/matrix-dart-sdk
-
Notifications
You must be signed in to change notification settings - Fork 0
Update SDK #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Airyzz
wants to merge
192
commits into
main
Choose a base branch
from
voip
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update SDK #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should speed up loading the archived rooms. One of the reasons it was so slow, is because we were loading all room members! Additionally this may work around a bug in Synapse, where rooms stuck in their partial state may block sync indefinitely. Relates to famedly/product-management#2250
fix: also lazy load members for archive
This was triggered by some archive decryption test I was writing and possibly also is triggered in production a few times. Waiting for running transactions to complete before closing sounds sensible.
When decrypting the last event for archived rooms when a room key is received, we used to send a synthetic SyncUpdate. This however put the archived room into the join section, which converted the room to a joined room. We need to respect what section the room was in when sending synthetic SyncUpdates. fixes famedly#1916
…ecoming-joined fix archive rooms becoming joined
feat: BREAKING CHANGE v1.11 support
chore: release v0.33.0
…cted-sender-debug-log chore: Lower loglevel for call event with unexpected sender
This was added in 77be610 without much documentation. I am pretty sure the intent was never to slow down every test by 5 seconds, so let's get rid of it and do more careful delays where it is useful (like specific sync requests for example). Makes the tests run 5 times faster (the whole suite!) on my device.
This reduces CPU load of the uploadKeys callback by a lot, since we don't upload new keys on every empty sync in the tests.
We do the key upload asynchronously without awaiting it. This means we may do multiple syncs before the key upload finishes. So we may generate more keys than we should. To fix that prevent multiple key uploads from running at once. This may lead to outdated key uploads in some cases if we miss an OTK being used in sync. However, the next sync will still tell us about that so in the worst case this might delay key uploads by 30s (with the default sync timeout), which for normal usage should be completely acceptable.
Might also fix our weird test hangs
Speedup tests
…d encrypt the file
…pload-content-does-not-e2ee chore: Make more clear that Client.uploadContent() does not end to end encrypt the file
…ark-unread refactor: Migrate to m.marked_unread from Matrix v1.12
The problem here is that we have not created a deep copy of the power level map. By using .copy() we create a deep copy now.
fix: Change power level without changing memory
Otherwise we were skipping the emoji tests without crypto set up and similar, which was not intentional.
It is not clear why we ever would want to return the formatted_body when we ask for the body, but it seems to not be used anywhere and there are no tests covering that functionality. However it leads to suprising results, where the plaintextBody can be tricked into returning html without applying conversions. So we just get rid of that functionality.
Covers a few edge cases that still fail. Changes to the unlocalizedBody function shouldn't cause behavioural changes apart from fixing a few edge cases.
We used to randomly return an empty string when the formatted body was empty, even though we never return an empty string usually. Similarly we used to return the original formatted body in an edit, when the new event has no formatted body.
Fixes some noise around logs when I was trying to enable branch coverage.
…ot-override-state-on-fetch-history fix: Older state events overwrite newer ones on fetching history
…d throw exception if room membership is not join
refactor: Make markUnread a noop if unread is already as intendend and throw exception if room membership is not join
…lizations chore: Export event localizations
…y-template chore: Remove unnecessary template
…or-restricted-rooms feat: Add parameter for allow condition for restricted rooms
…grade-room feat: Add command to upgrade room
fix: incorrect mimeType for files when downloading
fix: room prev_batch set incorrectly
fix: incorrect filename when caption is used in body of event
fix: room prev_batch set incorrectly follow-up
…ore-sending refactor: Add file info to placeholder before sending file event
feat: upload code coverage to codecov
this method isnt available on linux
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.