Feature Request + Bug Report:
I have to restart my pager multiple times every day, because it seemingly loses its connection to the hub, and once this happens it never reconnects. I then no longer receive notifications about forum/tracker replies, and if I attempt to join or download a game it gives me a connection failed message, or just hangs forever.
I really have no reliable information or method to cause this bug to happen, but its sure as hell there. I think it may actually be caused by following the notification links that the pager itself posts for me, they are definitely causing various other problems.
I've only been up for about an hour today, and it had already happened before I attempted to update my BYOND version (after checking my forums):
Downloading BYOND (3190017 bytes).
BYOND Hub: connection failed.
Your network connection is not working or the hub server is down.
What I'm requesting is (yet again) something like Steam does. The pager will occasionally test its connection to the hub. Once it finds that it is dead, it will output a single message to the user about such troubles, and that it is going to attempt fixing itself (unless it manages to fix itself at the same time the detection is made). It will then silently attempt to reconnect to the hub until it manages to, at which point it will output a notification that it has successfully reconnected.
While the pager is in this reconnecting state, it should have some sort of visual que. ie: where it says Falacy [Public] it could say Falacy [Reconnecting]
ID:99788
 Aug 4 2010, 5:01 am
|
|||||||||||||
Resolved
| |||||||||||||
|
Aug 4 2010, 5:56 am
|
|
Lummox JR
  |
The pager doesn't keep a persistent connection up. It sounds like it's having trouble reconnecting.
|
After the pager's connection has failed at life, if I have any lingering notifications about replies in it, and click them, it takes me to the "Login failed! Incorrect login info from pager." page.
| |
I thought it was just my netgear failing like it usually does and the pager not reconnecting. Apparently this issue is more wide-spread than I thought.
| |
Please fill out a bug report template. Another user has stated that these problems are occurring more frequently "recently" (not sure what that means). Is that the case with you, or has this always been a problem?
| |
This issue has been around for a long time to some degree. I think it got a lot worse in 472. It now happens literally every day, multiple times per day.
Though I'm not 100% sure about such things, and I've been awake for 30+ hours, so we'll see how the cookie crumbles. | |
Tom wrote:
Please fill out a bug report template. Another user has stated that these problems are occurring more frequently "recently" (not sure what that means). Is that the case with you, or has this always been a problem? For me it's always been a problem, but I just didn't bother with it at the time, as I didn't really develop much at the time. :/ | |
Falacy wrote:
This issue has been around for a long time to some degree. I think it got a lot worse in 472. It now happens literally every day, multiple times per day. It happened to me with 471, I'm sure of that. It's always happened before, but now it -is- doing it like every day. | |
Falacy, can you try downgrading to 471 and running that for a day to see if it makes a noticeable difference? In the meantime, we'll see if there's anything in 472 that could have worsened this issue. It is odd that it would have problems reconnecting while the hub is still pingable.
| |
I've had this problem as long as I can remember, but never as bad as its been recently. And it surely hasn't been 2 months worth, so it must have been 472.
I'm about to go to sleep, but I can throw 471 on and leave my computer up while I do. I've also tried to diagnose this bug multiple times before, but haven't managed to get any type of reliable, or actually any results at all that cause it to happen. So I never bothered filing a report. Now that it seems to be widespread, maybe somebody can catch on to it. Though, I'll say, completely powering off my router and/or my modem doesn't seem to cause it, spam clicking links in the pager doesn't seem to cause it. It may be caused by a mix of clicking notification links in the pager while browsing the site at the same time, but I'm pretty much doing that right now and it doesn't seem to be causing a problem. | |
Someone on Chatters has told me that if your internet connection disconnects, you should restart your pager, I've done that and it works fine, but I don't understand why I should have to do that every time..
| |
It is possible that a non-standard internet disconnect has been causing it in the past. One of the kinds that windows doesn't seem to notice?
But the recent issues surely aren't being caused by that, at least not on my system. I'm thinking it could have something to do with the system that prevents pop-ups and sounds when in a full-screen app. Since I think the last few times I had come back from playing WoW my pager was taking a vacation. | |
Yeah, the pager doesn't use a persistent hub connection so it shouldn't have an issue when there is a disruption. But that's something we can test.
| |
It doesn't seem to happen to me from doing anything, but rather from a lack of doing things. I'll come on after some time of inactivity during the day, click to play a game, and it will tell me that BYOND central isn't accessible. I think the pager just periodically disconnects or something.
| |
I could be active throughout most of the day, and it'll still happen to me, so I don't think that'd be the issue, I find myself I have this time to actually download resources for my project, so I'm going to take advantage of it now.
| |
Pretty sure my pager just took a flop, as it didn't notify me of the last 2 posts in this topic. I'm also pretty sure I had just restarted it before this discussion got started o.O like 10 minutes ago? (because it was dead)
Anything you want me to smack it with for testing, Tom? EDIT: Yup its definitely dead again, and yup I had just restarted it about 30 minutes ago to revive it from that death. I haven't played WoW, so maybe we can rule out the full screen thing =P | |
Well, we can simulate dead connections and see if that causes any issues, along with other tests. If nothing comes out of that, we can prepare a debug version for you to get some more information when the pager gets stuck like that.
| |
Hm, it notified me about that post you just made o.O
OK, well then, I'm gonna say its due to somehow getting logged out of the website? Since logging back in seems to have fixed it. Maybe I didn't restart it 30 minutes ago after all, maybe I just logged back in to that "Login failed! Incorrect login info from pager." page? But normally browsing the website doesn't have a problem. Only if I click a link from the pager. Which makes sense based on what that page's error message says... maybe... | |
I don't think it's the site. The site is the place I find all the stuff I missed while the pager was down. Actually, I often find stuff being redirected to the site too during the middle of a conversation. I need to check the site whenever I have a pager conversation because messages will often get redirected to the site instead of my pager. That's for another day though, probably.
| |