-
Notifications
You must be signed in to change notification settings - Fork 10
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
Figure out the connectivity problems #12
Comments
Hey, I seemingly have this issue on Google Chrome Version 48.0.2564.103 (64-bit), OS: Arch Linux64. If there's any information/data I can provide you with to resolve this ask away :) |
Hey @fedexcain. Thanks for chiming in here! I think I figured out the problem. Apparently if you visit Thank you 😃 |
Hey! Hope this helps, thanks for the quick fix and the very useful extension! |
@fedexcain Hooray! Thanks for this info, it's helpful. I'll leave this bug open for now (until v4.0 perhaps), and see if I can figure out a good way to reproduce. In the meantime, #15 might help make sure this isn't still happening. |
OK. I was able to reproduce, step through with the debugger, and think I figured out what's going on. There was a bug in the error handler, causing a loop and mis-reporting it as being in a bad state. That was all refactored and cleaned up, so the v4.3.0 version released just now should be more reliable than previous versions. Anyone, feel free to re-open if this persists and I'll dig deeper. |
Hi, I'm using the extension for a week now. I see this issue often. It is solved by restarting the browser but I figured you might find a permanent fix. Other than that I'm super happy happy, thanks a lot. Browser: Vivaldi 1.10.867.48 (Stable channel) (64-bit) OS: Windows 10 Creators Edition. Let me know if I can be of any help. Thanks! Edit: Also, there are times that the icons turns to blue again suddenly, with no apparent reason. |
There's several reviews that say that the extension remains gray like it can't connect. This issue is dedicated to figuring out why.
The text was updated successfully, but these errors were encountered: