Author Topic: bot errors off the lastest svn (Read 3892 times)

Nytridr · « **on:** September 18, 2007, 09:10:10 pm »

aotf [2007-09-18 19:00:11]      [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1889971348
aotf [2007-09-18 19:00:11]      [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1889971348
aotf [2007-09-18 19:00:11]      [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1889971348

This is just one bot, but this is happening across all raid bots I run, and similare problems with the org bots.

and this is happening over and over again on another org bot I run..

Code: [Select]

Noidbot1 [2007-09-18 19:06:54]  [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1822208007
Noidbot1 [2007-09-18 19:06:54]  [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1822208007
Noidbot1 [2007-09-18 19:06:54]  [GROUP] [MSG]   [The Noid] : Bot is online ::: R
oster update starting ::: System busy
Noidbot1 [2007-09-18 19:06:56]  [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1822208007
Noidbot1 [2007-09-18 19:06:56]  [GETUNAME]      [FAILED]        I was unable to
get the user name belonging to: -1822208007
Noidbot1 [2007-09-18 19:06:56]  [GROUP] [MSG]   [The Noid] : [The Noid Guest] :
[The Noid] : [The Noid Guest] : [The Noid] : [The Noid Guest] : [The Noid] : [Th
e Noid Guest] : [The Noid] : [The Noid Guest] : [The Noid] : [The Noid Guest] :
[The Noid] : [The Noid Guest] : [The Noid] : [The Noid Guest] : [The Noid] : [Th
e Noid Guest] : [The Noid] : [The Noid Guest] : [The Noid] : Bot is online ::: R
oster update starting ::: System busy

finally had to shut everything down.. Seems like this if from the roster update part.. it dont seem to be able to get roster updates.. and you cant pull it from FC..

Code: [Select]

Not Found

The requested URL /org/stats/d/1/name/6709250 was not found on this server.

need to have a way to get past this.. expecially when you drop the user table and the FC site isnt advalible

Blueeagle · « **Reply #1 on:** September 18, 2007, 09:37:04 pm »

I'm so sorry about that. It was a not-too-well tested update.

As of 1063 (just committed to the SVN) it should be fixed I hope. Unfortunately I haven't made a complete test-set for that wrapper so I am mostly hopinig.

Nytridr · « **Reply #2 on:** September 18, 2007, 09:44:01 pm »

I will repull and let ya know... OK it is good so far.. I am bring up the bots now.. and will watch to see if there is any other problems

Alreadythere · « **Reply #3 on:** September 18, 2007, 09:57:45 pm »

Let me put a warning in here - you cannot rely on SVN being stable. Most of the times the commits are tested, but there may be commits that will (perhaps even knowingly) break the current branch, especially if large internal changes are done.

The 0.4 branch on the other hand should only contain tested stable code at all times.

Nytridr · « **Reply #4 on:** September 18, 2007, 10:01:20 pm »

Quote from: Nytridr on September 18, 2007, 09:44:01 pm

I will repull and let ya know... OK it is good so far.. I am bring up the bots now.. and will watch to see if there is any other problems

looks good.. ty for the fix

Nytridr · « **Reply #5 on:** September 18, 2007, 10:06:30 pm »

Quote from: Alreadythere on September 18, 2007, 09:57:45 pm

Let me put a warning in here - you cannot rely on SVN being stable. Most of the times the commits are tested, but there may be commits that will (perhaps even knowingly) break the current branch, especially if large internal changes are done.

The 0.4 branch on the other hand should only contain tested stable code at all times.

I know this..

but you all are so uber, that I know I trust ya. I always make a backup of it before I update, so if it dose happen then it isnt a problem..

Blueeagle · « **Reply #6 on:** September 18, 2007, 10:14:37 pm »

Also svn update does support a --revision argument and you can browse the SVN checkins by following the link on the left. So you can revert back until the error goes away and then you know which commit broke the bot.

Not sure if you can revert one single file tho.