zippynk wrote:
I suggest reverting to an old version of the code until the bug is found.
(Ohaider agrees.)
Since you both agree, I agree as well. MolyBot does too However, playzooki also does
EDIT: Page 8!
Supporters:
ohaiderstudios
zippynk
Molybdenum
MolyBot
playzooki
Last edited by Molybdenum (2012-10-06 21:57:41)
Offline
I'll revert next week on Tuesday.
Offline
Molybdenum wrote:
zippynk wrote:
I suggest reverting to an old version of the code until the bug is found.
(Ohaider agrees.)Since you both agree, I agree as well. MolyBot does too However, playzooki also does
EDIT: Page 8!
Supporters:
ohaiderstudios
zippynk
Molybdenum
MolyBot
playzooki
I agree, but thats not a bad thing, you just hate me. The current one is hit and miss.
AND SO DOES UJ!
Offline
Bump.
I found the problem!
When a user uses commands, the server gets stuck in an infinite loop!
(oh wait, did you already know that? I really thought I had a breakthough )
Last edited by Molybdenum (2012-10-07 19:24:37)
Offline
Molybdenum wrote:
Bump.
I found the problem!
When a user uses commands, the server gets stuck in an infinite loop!
(oh wait, did you already know that? I really thought I had a breakthough )
That was our working theory, yes.
But it encourages me to see the same people discovering similar things separately.
So basically...it was a victory in its own way.
Last edited by ohaiderstudios (2012-10-07 23:33:32)
Offline
ohaiderstudios wrote:
Molybdenum wrote:
Bump.
I found the problem!
When a user uses commands, the server gets stuck in an infinite loop!
(oh wait, did you already know that? I really thought I had a breakthough )That was our working theory, yes.
But it encourages me to see the same people discovering similar things separately.
So basically...it was a victory in its own way.
Thanks I figured it out by trying commands (Sorry, I know I wasn't supposed to do that, but the servers all better now), realizig that I, and everyone else, couldn't chat, so the "server message bouncer" part of the server was disabled.
Offline
Magnie wrote:
I'll revert next week on Tuesday.
Thank you sooooo much Magnie! We all appreciate the trouble you go through so we can waste time chatting with people we've never met!
No but seriously, thanks!
Offline
ohaiderstudios wrote:
Magnie wrote:
I'll revert next week on Tuesday.
Thank you sooooo much Magnie! We all appreciate the trouble you go through so we can waste time chatting with people we've never met!
No but seriously, thanks!
... Anyway, tuesday is tommorow!
Offline
Molybdenum wrote:
ohaiderstudios wrote:
Magnie wrote:
I'll revert next week on Tuesday.
Thank you sooooo much Magnie! We all appreciate the trouble you go through so we can waste time chatting with people we've never met!
No but seriously, thanks!... Anyway, tuesday is tommorow!
Yes...yes it is. Don't let anyone tell you differently.
Offline
Its tuesday!
And its still broken. You there Magnie?
Details: Everything worked for a little while, then everything broke.
Offline
Do you have any details other than that?
I reverted back, though I think I've given up on trying to auto-disconnect users for now and replaced the (probable) broken loop with a part channel instead. I haven't tested it though.
Offline
Magnie wrote:
Do you have any details other than that?
I reverted back, though I think I've given up on trying to auto-disconnect users for now and replaced the (probable) broken loop with a part channel instead. I haven't tested it though.
I will! EDIT (Yes! Another edit!): Not working.
Last edited by playzooki (2012-10-10 14:20:02)
Offline
Magnie wrote:
Do you have any details other than that?
I reverted back, though I think I've given up on trying to auto-disconnect users for now and replaced the (probable) broken loop with a part channel instead. I haven't tested it though.
Chatted with some test posts, MolyBot worked, /list, and it worked (I was only one in scratch), /list-all, worked (I was only one online), tried to chat again, nothing worked. Rejoined, didn't work.
Offline
I think I'm going to recode server.py with the greenlet module instead of full blown threads. Though I'll need to learn a little more about them before I do it.
Offline
Magnie wrote:
I think I'm going to recode server.py with the greenlet module instead of full blown threads. Though I'll need to learn a little more about them before I do it.
Yay.
Offline
Magnie wrote:
I think I'm going to recode server.py with the greenlet module instead of full blown threads. Though I'll need to learn a little more about them before I do it.
Use Stackless Python!
Offline
blob8108 wrote:
Magnie wrote:
I think I'm going to recode server.py with the greenlet module instead of full blown threads. Though I'll need to learn a little more about them before I do it.
Use Stackless Python!
I'm tempted to, but my host doesn't have it.
Offline
Magnie wrote:
blob8108 wrote:
Magnie wrote:
I think I'm going to recode server.py with the greenlet module instead of full blown threads. Though I'll need to learn a little more about them before I do it.
Use Stackless Python!
I'm tempted to, but my host doesn't have it.
You can't install it? Meh.
Oh, and have you tried Twisted yet?
Offline
blob8108 wrote:
Magnie wrote:
blob8108 wrote:
Use Stackless Python!I'm tempted to, but my host doesn't have it.
You can't install it? Meh.
Oh, and have you tried Twisted yet?
No, sorry for being so stubborn.
Offline
Found a bug: When a user leaves, the "X has left room Y" is not broadcast. So when a user chats after a user leaves and the leave message is not displayed, his message is overode with the leave message.
Offline
Magnie wrote:
blob8108 wrote:
Oh, and have you tried Twisted yet?
No, sorry for being so stubborn.
Oh. How disappointing.
Offline
Chat.PY doesn't seem so "reverted" to me...
Offline
ohaiderstudios wrote:
Chat.PY doesn't seem so "reverted" to me...
No idea what's going on. But with greenlet's timeout features, client commands will be resilient hopefully.
Offline
Magnie wrote:
ohaiderstudios wrote:
Chat.PY doesn't seem so "reverted" to me...
No idea what's going on. But with greenlet's timeout features, client commands will be resilient hopefully.
I thought the plan was to revert to 2.0?
If not, sorry for the accusation, but nothing's fixed.
Offline