search

devBuzzy / pircbotx

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

onConnect misfire. #99

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. implement onConnect() to read 'System.out.println("onConnect!");'
2. connect to a server that requires SASL when connecting from Mexico
3. watch the fireworks.

What is the expected output? What do you see instead?
Expected: clean disconnect, no "onConnect!" to appear.
Seen: "onConnect!" appears in console.

What version of the product are you using? On what operating system?
1.8-SNAPSHOT

Please provide any additional information below.
Please see http://paste.thezomg.com/6499/35637692/ for the console trace.

Original issue reported on code.google.com by entityreborn on 24 Dec 2012 at 7:24

GoogleCodeExporter commented 9 years ago 
Possible fix would be to fire onConnect when receiving a 001 response 
(RPL_WELCOME). Any handler that needs to know about successful socket 
connection can use onSocketConnected.

Original comment by entityreborn on 24 Dec 2012 at 7:25

GoogleCodeExporter commented 9 years ago 
Can you test this with the latest changes? handleLine will now shutdown the bot 
when it receives an ERROR line. I tried testing with tor but had trouble 
getting it working

Original comment by Lord.Qua...@gmail.com on 7 Jan 2013 at 11:30

GoogleCodeExporter commented 9 years ago

Original comment by Lord.Qua...@gmail.com on 10 Jan 2013 at 10:14