search

raisedragon / pircbotx

Automatically exported from code.google.com/p/pircbotx
0 stars 0 forks source link

Channel mode is stale on channel part/quit (PircBotX can't handle certain channel modes) #208

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
As far as I can tell this is different from the recently closed issue.

What steps will reproduce the problem?
1. Have the bot join at least one channel that has modes with additional 
parameters. For example +ntj 3:5 (MODE #test => #test +ntj 3:3).
Hard mode: +ntfj [12j#i15]:10 3:6
+j 3:6
+f [12j#i15]:10 (12 joins in 10 seconds results in +i for 15 seconds)
https://www.unrealircd.org/files/docs/unreal32docs.html#feature_antiflood

2. Part/Quit and rejoin a channel (doesn't have to be the one with +j) the bot 
is in.

3. Every part/quit onwards will result in: 
[main] WARN org.pircbotx.Channel - Channel #test mode '+XYZ' is stale
regardless if that was the channel the user quit/parted from.

What is the expected output? What do you see instead?
I'm not sure if the bot is meant to warm that it doesn't know what advanced 
settings the channel has on every part/quit.

What version of the product are you using? On what operating system?
pircbotx-2.1-20141104.023805-64.jar

Please provide any additional information below.
This result can be reproduced on (at least) the following servers: 
Unreal3.2.9 (DorksNet)
Charybdis (Esper)

Original issue reported on code.google.com by Tnade...@gmail.com on 4 Nov 2014 at 9:34

GoogleCodeExporter commented 9 years ago 
+f seems to be an Unreal thing. +f on Charybdis is forward. Also takes an 
argument though.

Original comment by Tnade...@gmail.com on 4 Nov 2014 at 9:37

GoogleCodeExporter commented 9 years ago 
Herp. Issue #27 is this issue minus the stale warnings. Do what you will with 
this.

Original comment by Tnade...@gmail.com on 4 Nov 2014 at 10:28

GoogleCodeExporter commented 9 years ago 
I cannot reproduce this. I tried on Freenode with a simple "+f #pircbotxtest" 
(flood channels) that adds arguments and triggers the mode stale warning. 
However it correctly only appears once. 

Can you attach the full log of when this happens?

Original comment by Lord.Qua...@gmail.com on 4 Nov 2014 at 9:43

GoogleCodeExporter commented 9 years ago 
Still can't reproduce, closing. If you run into this again let me know and I'll 
re-open this

Original comment by Lord.Qua...@gmail.com on 18 Nov 2014 at 6:05