Skip to content
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.

Sign up for GitHub

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

Jump to bottom

verifier still sends a timeout after having verified #12043

Closed
bwindels opened this issue Jan 24, 2020 · 5 comments
Closed

verifier still sends a timeout after having verified #12043

bwindels opened this issue Jan 24, 2020 · 5 comments
Assignees
@bwindels
Labels
A-E2EE-Cross-Signing

Comments

@bwindels
Copy link
Contributor

bwindels commented Jan 24, 2020 •
edited
Loading

after having successfully verified davetest (which now is indeed verified, the verify button doesn't appear anymore), both their and my client send a .cancel with m.timeout after about 7 minutes after sending the .start event.
@bwindels
Copy link
Contributor Author

can't repro anymore

@bwindels
Copy link
Contributor Author

Can't repro anymore

@bwindels
Copy link
Contributor Author

bwindels commented Feb 1, 2020

this still seems to happen, apparently in non-e2ee rooms

@bwindels bwindels reopened this Feb 1, 2020
@bwindels bwindels mentioned this issue Feb 4, 2020
Closed
@jryans jryans added the phase:2 label Feb 10, 2020
@bwindels
Copy link
Contributor Author

also, the request timeout doesn't seem to work anymore. Leaving riot open after accepting (.ready) never seems to cancel with timeout.

@bwindels bwindels self-assigned this Feb 18, 2020
@bwindels
Copy link
Contributor Author

bwindels commented Feb 20, 2020 •
edited
Loading

I tried both in e2ee and non-e2ee DMs, could not reproduce. Only problem I found was #12434 (which is explains the comment above) so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwindels bwindels

Labels
A-E2EE-Cross-Signing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bwindels @jryans