Board timing issues?
- Thread starter DrakeM
- Start date
Normally, when this issue is happening, we get a lot of complaints, this time however it is only you (DrakeM) and John.
That does not mean there aren't more people with the same issue of course but usually we would get email with complaints and there would be several threads opened on the board about it.
So, another possibility could be your FreeOnes cookies are corrupt, try to clean your browser cache and cookies.
Or you could even try a different browser and see if the same problem happens.
If you can give that a try and let me know it helped that would be great.
That does not mean there aren't more people with the same issue of course but usually we would get email with complaints and there would be several threads opened on the board about it.
So, another possibility could be your FreeOnes cookies are corrupt, try to clean your browser cache and cookies.
Or you could even try a different browser and see if the same problem happens.
If you can give that a try and let me know it helped that would be great.
DrakeM
So long and thanks for all the fish
Happening again today. Right after a successful post that took five attempts, I logged out, cleared my cache and cookies and logged back in. Next attempted post, same problem, and this post took two attempts to get posted.
Last edited:
DrakeM
So long and thanks for all the fish
The only other hint I can give you is that it seems like there are multiple servers or ports or something each with a different time difference. For example, just now I tried to post something and got "wait 128 seconds". The next attempt said "wait 15 seconds" then "wait 85 seconds" then "wait 11 seconds". To me, it looks like there are three ways into the posting system, one in sync with me and two others out of sync, but I'm guessing. Multiple attempts do seem to have them count down as you would expect but from different starting points until I get lucky and hit the one in sync with me. All this is guesswork though and it happens randomly. Often I've got no problem at all for several minutes.
I will report your findings to the tech guy again, but I can't promise he will have a look any time soon.
DrakeM
So long and thanks for all the fish
Okay, but it is still happening today. First two posts were fine then the third got the problem. Using Firefox if that helps.
I am sorry you are having problems with posting but as I said before, this has been reported.
However there's only 1 tech guy, his list of things to do is huge and board problems are unfortunately not high on his priority list.
However there's only 1 tech guy, his list of things to do is huge and board problems are unfortunately not high on his priority list.
DrakeM
So long and thanks for all the fish
Still happening every day, very frustrating at times. If I was running the board I'd insert some code that says "If I'm about to print a message saying you have to wait more than 10 seconds, the board is screwed up and just let the post go through and maybe log the conditions"
I understand this is frustrating but all we can do is wait until the tech guy has time to pick up this issue.
DrakeM
So long and thanks for all the fish
This is still happening every day but it is tolerable in that only every 5-10 posts will show the problem and then you can usually get the post through on the 2nd or 3rd attempt. The time difference though is fairly consistent on each occurrence, usually between 180 and 220 seconds printed that I have to "wait between posts".
I really think this is a problem on your end because if this was wide spread we would receive many complaints about this every day and we haven't.
DrakeM
So long and thanks for all the fish
In all due respect, you might be right but that would imply that somehow the board is using timestamps from my computer or allowing my computer to manipulate them. Either way, that's a terrible design. I find it more likely that something is corrupting timestamps within the board itself and it is an intermittent problem that my particular account is more prone to trigger. If you've ever written any decent amount of code, you've seen this kind of problem dozens of times with a bad or stale pointer using memory it shouldn't that may or may not cause bad effects. To me, this is a classic case of that. I wait to be proven wrong.
I'll give you a real life example I was involved with. Customer complained our code failed on his system. We couldn't reproduce the problem so got access to that particular system and started to diagnose it. Turns out that only on that system for whatever reason, a particular memory location would sometimes contain the number 16 instead of 0. We had a wild pointer that used that value (although it shouldn't) and 0 was fine but 16 was bad. We fixed the pointer issue to point to the right place and the bug was solved. I've also had to diagnose issues where code would fail if the command line parameter size went past a certain size. It made no difference whatsoever what the parameters were, just that they went past a certain size thus shifting memory slightly and a wild pointed again picked up a bad value. Maybe "DrakeM" is too short as most other IDs are longer. End of programming lesson.
