-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Element-R: await /keys/query
during Verification requests
#3932
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sensible, but I need a little more explanation to understand it I think.
@@ -322,6 +333,10 @@ export class RustVerificationRequest | |||
throw new Error(`Unsupported verification method ${method}`); | |||
} | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the critical part that causes us to avoid the race? If so, can we have a comment here explaining that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, sorry. Have added a comment.
This should now be fixed, thanks to matrix-org/matrix-js-sdk#3932.
This should now be fixed, thanks to matrix-org/matrix-js-sdk#3932.
If the acceptance of an incoming verification request races with a
/keys/query
for the other user, then subsequent operations can fail (see matrix-org/matrix-rust-sdk#2896).This is a slightly hacky workaround that means we wait for the devicelist to arrive for the relevant operations.
Required for a fix to element-hq/element-web#26420.
This change is marked as an internal change (Task), so will not be included in the changelog.