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

Hitting Retry on Signature Upload Failed dialog does nothing #13287

Open
anoadragon453 opened this issue Apr 20, 2020 · 5 comments
Open

Hitting Retry on Signature Upload Failed dialog does nothing #13287

anoadragon453 opened this issue Apr 20, 2020 · 5 comments

Comments

@anoadragon453
Copy link
Member

anoadragon453 commented Apr 20, 2020

Description

During testing of matrix-org/synapse#7276 I get the following error dialog, which is definitely helpful for debugging!

image

However, hitting retry seems to produce no network request, and hitting retry a second time then just pops up the following dialog:

image

Logs being sent: yes no. Getting the following when trying to send logs:

image

And refreshing seems to say that my local database is having issues: Turns out running two Riots in the same browser context does bad things to your database.

image

Version information

  • Platform: web
  • Browser: Firefox Nightly
  • OS: Linux
  • URL: riot.im/develop
@anoadragon453
Copy link
Member Author

To be clear, it seems that hitting Retry here corrupts my database(!), and Clear Cache and Reload doesn't fix it. Only logging out and in again does.

@jryans
Copy link
Collaborator

jryans commented Apr 20, 2020

Tracking post-release for now. @anoadragon453, does it reliably cause database issues, or was that part a one-off fluke?

@anoadragon453
Copy link
Member Author

Ahhh, I'm using two matrix accounts in the same Firefox context. That's probably what's causing the database corruptions lol.

Let me retest without that.

@anoadragon453
Copy link
Member Author

anoadragon453 commented Apr 20, 2020

Hm, well I don't get the Something went wrong! message on refresh anymore, but submitting logs does result in an "No connected database" still.

And that doesn't go away even after logging in and out... so going to assume something else is causing that. Is there any other way I can get debug logs to you guys ooi?

@jryans
Copy link
Collaborator

jryans commented Apr 20, 2020

@anoadragon453, let's move the log database issues to #13290.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants