Closed gte619n closed 7 years ago
I can confirm this behavior on Chrome on Ubuntu as well. For now I just disabled the extension. I would not say this is a critical bug but it should be addressed sooner rather than later.
I pushed 0.71.3 -- @gte619n @chiamarc can you let me know if it is still happening with that version once you get it? Thanks and sorry for the trouble.
No apologies necessary! You've got a great plugin!
On Tue, Mar 14, 2017 at 9:34 AM, Steve Bussetti notifications@github.com wrote:
I pushed 0.71.3 -- @gte619n https://github.com/gte619n @chiamarc https://github.com/chiamarc can you let me know if it is still happening with that version once you get it? Thanks and sorry for the trouble.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sbussetti/deluge-siphon/issues/47#issuecomment-286422137, or mute the thread https://github.com/notifications/unsubscribe-auth/AANqnGy7LTApSycEsnoo-1kogjPeI_zYks5rlpdvgaJpZM4MbMXc .
Just pushed another update, 0.71.4 that should further improve this issue. And thanks for using my extension.
I'm noticing the same behaviour, anyway to add an option to disable connection messages for users on multiple networks? I'm on version 0.71.4 and the popups are persistent at work.
If it helps I have attached the messages they happen in order every 30 seconds or so.
Message 1:
Message 2:
@thehaxxa yeah I have support for multiple connections in the works, but not complete yet. I adjusted the messages to try and get a better idea what the issue is -- Thanks for the screenshots. It's related to the auto-login logic I added to address #45 . I'm going to make some more adjustments and push another update shortly.
Just put v 0.71.5 in the hopper. It should reduce if not completely resolve this verbose notification issue. LMK how it goes.
Steve, pardon my ignorance, but is there a way to force chrome to update or do we just have to wait?
On Mar 15, 2017 9:24 AM, "Steve Bussetti" notifications@github.com wrote:
Just put v 0.71.5 in the hopper. It should reduce if not completely resolve this verbose notification issue. LMK how it goes.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sbussetti/deluge-siphon/issues/47#issuecomment-286739677, or mute the thread https://github.com/notifications/unsubscribe-auth/AANqnGj4-ensqSkDcAM6qzIBwRlApj1iks5rl-aMgaJpZM4MbMXc .
@gte619n little bit of both. I'll ping on this thread once Google tells me they are done scanning and publishing the update. Once that's complete it gets pushed out pretty soon.
Ways to force your chrome to update extensions (after I let you know that Google is done scanning my code):
A. Quit and restart Chrome (all windows)
B. Go to: chrome://extensions/ and refresh the page with control/command + r
@gte619n okay, update is past the Chromey gatekeepers. Should be down to you soon.
I'm on a network outside of the location of my server. The plugin is constantly popping up connection error messages. These mesages are the Chrome Notification popups in the lower right corner. This is new behavior.