search

urbit / bridge

An application for interacting with Azimuth.
MIT License
96 stars 25 forks source link

{"code":7979,"data":{}} #973

Closed baudtack closed 2 years ago

baudtack commented 2 years ago

Didn't use meta mask, just trying to log in with a bip39. crashes like this in both firefox and chrome. it was working fine and then i tried to transfer some eth to the address in question to perform a transaction and got this.

tomholford commented 2 years ago

@baudtack Thanks for flagging this issue. Unfortunately, I was not able to reproduce. Here are the steps I tried:

  1. Log in with mnemonic
  2. Select an L1 star from the family view, then navigate to Star Ops > Spawn Planet
  3. Spawn an L1 planet, wait for the TX to process, then navigate to family view and confirm it is present
  4. Select the newly spawned L1 planet, click Set Network Keys in the modal, wait for the TX to process, and confirm that the keys are set
  5. Navigate back to family view, select an L2 star, then navigate to Star Ops > Spawn Planet
  6. Spawn an L2 planet, wait for the TX, and confirm it is now present in the family view

When you have a chance, can you share any other steps you might have taken to reach this error state? Thanks

tomholford commented 2 years ago

@baudtack When Bridge prompted to enable broswer notifications, did you accept or decline? Have a hunch it might be related

arthyn commented 2 years ago

@tomholford I think it has to do with the roller timing out connections. That seemed to be going on around when this was posted.

PR0M3TH3AN commented 2 years ago

I'm having this same issue. Cant login to bridge

tomholford commented 2 years ago

@PR0M3TH3AN Thanks for the report, we just pushed a performance optimization to Bridge. Can you try again and report back?

PR0M3TH3AN commented 2 years ago

@PR0M3TH3AN Thanks for the report, we just pushed a performance optimization to Bridge. Can you try again and report back?

Thanks man! It's working again. You guys are awesome!

tomholford commented 2 years ago

This issue has been resolved by performance improvements in the roller (prioritizing timers over HTTP) and Bridge (#971)