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.

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

to_device message went missing from vdh->matthew with megolm session data #2711

Closed
Tracked by #2996
ara4n opened this issue Dec 7, 2016 · 5 comments
Closed
Tracked by #2996
Labels
A-E2EE P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@ara4n
Copy link
Member

ara4n commented Dec 7, 2016

2016-12-06 15:04:34.568 sharing keys with device @matthew:matrix.org:VACHRWKSRK
2016-12-06 15:04:34.568 Using sessionid 9Qn7CnpPkl4+GKsM1Wxry9SPNL8nF/FgbA2r8TOp8Nw for device @matthew:matrix.org:VACHRWKSRK

never made it through from vdh's riot-web to mine.

@richvdh
Copy link
Member

richvdh commented Dec 12, 2016

annoyingly I've now left it long enough that all the logs have been rotated :/

richvdh added a commit to matrix-org/synapse that referenced this issue Dec 15, 2016
Attempt to track down the loss of to_device events
(element-hq/element-web#2711 etc).
@ara4n ara4n added the S-Major Severely degrades major functionality or product features, with no satisfactory workaround label Dec 18, 2016
@lampholder
Copy link
Member

Do we have some logs available for this? Is it possible to make material progress with this issue, or is it waiting for a recurrence?

@lampholder lampholder added the X-Needs-Info This issue is blocked awaiting information from the reporter label Apr 3, 2017
@ara4n
Copy link
Member Author

ara4n commented Apr 3, 2017

waiting for a recurrence, unless richvdh thinks he's fixed a possible cause of to_device events going missing over federation somewhere along the line.

@richvdh
Copy link
Member

richvdh commented Apr 3, 2017

I don't think I did anything that would fix it, but given this hasn't been seen for months, I vote for closing it.

@lampholder
Copy link
Member

Agreed - we can always reopen if we see more instances.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

3 participants