Results 1 to 9 of 9

Thread: FAIL Alliance Rejoin Change

  1. #1

    Default FAIL Alliance Rejoin Change

    Clicked to invite a member through Whisper. This came up



    Been 25 hours, Fail
    Last edited by spooner1; 12-01-2011 at 08:48 PM. Reason: Edit out log times.

    "The World is for my plundering"
    Spooner, June 2011

  2. #2
    Join Date
    Nov 2010
    Location
    New England
    Posts
    1,269

    Default

    found you.

    I'll pass this on to QA.

    Flaming CHICKEN!
    Courtesy: Sturm

  3. #3
    Join Date
    Nov 2010
    Location
    New England
    Posts
    1,269

    Default

    Who was the member?

    Flaming CHICKEN!
    Courtesy: Sturm

  4. #4

    Default

    Quote Originally Posted by davemata View Post
    found you.

    I'll pass this on to QA.
    Quote Originally Posted by davemata View Post
    Who was the member?
    It fixed after we both refreshed, Not sure what that was about but problems solved.

    Feel free to close
    Last edited by spooner1; 12-01-2011 at 10:42 PM.

    "The World is for my plundering"
    Spooner, June 2011

  5. #5
    Join Date
    Sep 2010
    Location
    Hacking the Gibson
    Posts
    179

    Default

    Flash temp files can create that error ;-)

  6. #6

    Default

    In before the lock!

  7. #7
    Join Date
    Aug 2009
    Location
    Building a religion... a limited edition...
    Posts
    15,996

    Default

    What's a lock?

  8. #8

    Default

    Quote Originally Posted by Thantium View Post
    Flash temp files can create that error ;-)
    If it happens again ill clear my temp files.

    Thanks

    "The World is for my plundering"
    Spooner, June 2011

  9. #9

    Default

    Quote Originally Posted by spooner1 View Post
    If it happens again ill clear my temp files.

    Thanks
    This implies that you may not have done so before.

    An alternative explanation is that the variable used to check to see if rejoining is allowed is updated at initial program load or at other intervals, but the interval to check went beyond the possible range of values.

    An example from my past:

    A timer event was scheduled at + so many milliseconds. There are only so many milliseconds in a day (8640000). Just before midnight, one of the additions caused the value to be checked to be greater than 8,640,000. When the program then next attempted to check, it ran into a situation where the value was over the maximum possible value, thus the process' timer event would never happen again until such time as the program was restarted, thus obtaining on reloading a value that was in the appropriate range of possible values.

    Not every situation can be dismissed as nebulous "temp files". Sometimes the problem is with the program logic.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •