I just want to know when the server will...you know...ACTUALLY WORK!!!!
Not to sound whiny or anything
Offline
ohaiderstudios wrote:
I just want to know when the server will...you know...ACTUALLY WORK!!!!
Not to sound whiny or anything
Don't we all?
Offline
ohaiderstudios wrote:
I just want to know when the server will...you know...ACTUALLY WORK!!!!
Not to sound whiny or anything
I know the problem! Too much school work! >.<
Well, you can look at the code and tell me what´s wrong.
Offline
I got Chat.PY 3.0 to work.
tip: open multiple instances of the program
Offline
zippynk wrote:
First thing I notice:
How's virtual space doing?
I need to reformat it in my head.
Offline
The first thought that popped into my head when the problem happened this morning was, "Magnie changed the server and made a spelling error!" Which happened once before. However it could also have been any sort of exception thrown when a certain function was called.
Offline
ohaiderstudios wrote:
The first thought that popped into my head when the problem happened this morning was, "Magnie changed the server and made a spelling error!" Which happened once before. However it could also have been any sort of exception thrown when a certain function was called.
I was about to write an idea of what could be the problem. Then I realized, it´s probably an infinite loop in chat3.py where it´s removing dead clients. That would explain why no broadcasts reach the server, but you can still receive other broadcasts and updates.
Look at Server.server_message(), Server.channel_message(), Server.user_message(), and Server.lost_user(). That´s what I´ve been changing recently. I don´t know where the infinite loop is though.
Offline
Magnie wrote:
ohaiderstudios wrote:
The first thought that popped into my head when the problem happened this morning was, "Magnie changed the server and made a spelling error!" Which happened once before. However it could also have been any sort of exception thrown when a certain function was called.
I was about to write an idea of what could be the problem. Then I realized, it´s probably an infinite loop in chat3.py where it´s removing dead clients. That would explain why no broadcasts reach the server, but you can still receive other broadcasts and updates.
Look at Server.server_message(), Server.channel_message(), Server.user_message(), and Server.lost_user(). That´s what I´ve been changing recently. I don´t know where the infinite loop is though.
Also, I think there might be an infinite loop in the command part, although I don't lmpw where it is.
Offline
here's what I think:
there are 2 bugs.
the first is obvious. using any /commands breaks the server so you can't broadcast anything.
the second: because you exit scratch without actually "leaving" the chat room, when you come back it glitches. You have to open another instance of Chat.PY and use a different name.
Offline
zippynk wrote:
I think I might have found the bug. It uses the same variable ("i") for removing users and sending messages to clients.
(chat3.py, starting near line 100)
I hate when that happens
Offline
ohaiderstudios wrote:
zippynk wrote:
I think I might have found the bug. It uses the same variable ("i") for removing users and sending messages to clients.
(chat3.py, starting near line 100)I hate when that happens
Since i is just a counter, I´m recycling it. I´ve changed the second part to 'n' though. And I think I just figured out what´s wrong. I´ve been adding 'i' to the to_delete when I should have been adding user_id... I don´t even know why I am using 'i' in that part.. Oh well. Hopefully it´s fixed now.
Offline
Magnie wrote:
ohaiderstudios wrote:
zippynk wrote:
I think I might have found the bug. It uses the same variable ("i") for removing users and sending messages to clients.
(chat3.py, starting near line 100)I hate when that happens
Since i is just a counter, I´m recycling it. I´ve changed the second part to 'n' though. And I think I just figured out what´s wrong. I´ve been adding 'i' to the to_delete when I should have been adding user_id... I don´t even know why I am using 'i' in that part.. Oh well. Hopefully it´s fixed now.
ill test... EDIT: Yup
Last edited by playzooki (2012-10-01 15:02:33)
Offline
Ohaider, zippynk: It seems the bug is still occurring. I found a work-around though. Join another room, login, type /list-all then find /force-kill any of the users that may be dead ones. The bug also occurs in the automatic removal of a user.
Offline
Magnie wrote:
Ohaider, zippynk: It seems the bug is still occurring. I found a work-around though. Join another room, login, type /list-all then find /force-kill any of the users that may be dead ones. The bug also occurs in the automatic removal of a user.
Cant join a room
Offline
Still wont work. Nothing wrong with the code that i can find either.
Last edited by playzooki (2012-10-03 15:30:39)
Offline
Alright, you know what? I'm going to do a very thorough analysis of the chat3.py code and get back to you guys at an indefinite time in the future.
EDIT: Is the SVN repository code the absolute latest? Because I suspect that it was some mistake Magnie made on his last update that is causing these errors.
FIRST REPORT:
message = 'Channel names have a ' message += 'maximum length of 10 characters.'
lol?
Last edited by ohaiderstudios (2012-10-06 01:56:08)
Offline
ohaiderstudios wrote:
Alright, you know what? I'm going to do a very thorough analysis of the chat3.py code and get back to you guys at an indefinite time in the future.
EDIT: Is the SVN repository code the absolute latest? Because I suspect that it was some mistake Magnie made on his last update that is causing these errors.
FIRST REPORT:Code:
message = 'Channel names have a ' message += 'maximum length of 10 characters.'lol?
I did that to keep the line under 70 characters.
Offline
Magnie wrote:
ohaiderstudios wrote:
Alright, you know what? I'm going to do a very thorough analysis of the chat3.py code and get back to you guys at an indefinite time in the future.
EDIT: Is the SVN repository code the absolute latest? Because I suspect that it was some mistake Magnie made on his last update that is causing these errors.
FIRST REPORT:Code:
message = 'Channel names have a ' message += 'maximum length of 10 characters.'lol?
I did that to keep the line under 70 characters.
Ok
Anyway, can't really find anything wrong
Offline
ohaiderstudios wrote:
Magnie wrote:
ohaiderstudios wrote:
Alright, you know what? I'm going to do a very thorough analysis of the chat3.py code and get back to you guys at an indefinite time in the future.
EDIT: Is the SVN repository code the absolute latest? Because I suspect that it was some mistake Magnie made on his last update that is causing these errors.
FIRST REPORT:Code:
message = 'Channel names have a ' message += 'maximum length of 10 characters.'lol?
I did that to keep the line under 70 characters.
Ok
Anyway, can't really find anything wrong
Well, it has something to do with infinite loops and possibly something to do with an Exception somewhere in the code. I believe it also has something to do with removing clients that have disconnected but haven't been removed and when it removes them, it seems to just hang there.
Offline
Magnie wrote:
ohaiderstudios wrote:
Magnie wrote:
I did that to keep the line under 70 characters.Ok
Anyway, can't really find anything wrongWell, it has something to do with infinite loops and possibly something to do with an Exception somewhere in the code. I believe it also has something to do with removing clients that have disconnected but haven't been removed and when it removes them, it seems to just hang there.
I agree. When a user disconnects, it breaks all other users. I focused my search on those areas, however I can't find anything that could create an infinite loop, even though that's what it most likely is, because a user can receive but not send.
Some weird exception being called is a possibility. Have you read the server logs?
Offline
zippynk wrote:
(Ohaider agrees.)
Yes he does. He just didn't mention it before because he didn't want to inconvenience Magnie.
Offline