search

raisedragon / pircbotx

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

Error connecting to some servers #105

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. 
http://github.com/BranicYeti/YetiBot/src/main/java/uk/co/deityhosting/yeti/Main.
java
2. Code in there for connecting to a server will through the error below:

http://pastebin.com/GUcfCcPL

What version of the product are you using? On what operating system?
Operating System: Windows 7
IDE: NetBeans
PircBotX a.8-SNAPSHOT

Please provide any additional information below.

Original issue reported on code.google.com by BranicY...@live.co.uk on 4 Jan 2013 at 9:29

GoogleCodeExporter commented 9 years ago 
Ah, forgot to mention. This is only the case on some servers. Error occurred on 
Esper and Freenode, but not on a friends server (irc.carnerum.net)

Original comment by BranicY...@live.co.uk on 4 Jan 2013 at 9:30

GoogleCodeExporter commented 9 years ago 
Yes, this is mainly my fault. I've fixed thism, but for some reason, the 
sonatype repo hasn't updated to my fix, so I will discuss more with 
LordQuackstar about this.

Original comment by entityreborn on 5 Jan 2013 at 12:34

GoogleCodeExporter commented 9 years ago

Original comment by entityreborn on 5 Jan 2013 at 12:34

GoogleCodeExporter commented 9 years ago 
Sorry for multi-posting. A fix you can use for now is event.respond("CAP 
END");. This will allow your bot to continue connecting.

Original comment by entityreborn on 5 Jan 2013 at 12:36

GoogleCodeExporter commented 9 years ago 
Not a problem. I did find the closed ticket after submitting this one. I will 
look into that fix, but I would like something more permanent. Would it be too 
much to request a post here when son style updates? I'm unaware of any sort of 
public update announcer

Original comment by BranicY...@live.co.uk on 5 Jan 2013 at 12:43

GoogleCodeExporter commented 9 years ago 
If I remember, for sure.

I am definetly planning on a better mechanism for CAP, it's a tricky bugger to 
implement, apparently.

Original comment by entityreborn on 5 Jan 2013 at 12:45

GoogleCodeExporter commented 9 years ago 
Thank you. And good luck.

Original comment by BranicY...@live.co.uk on 5 Jan 2013 at 2:31

GoogleCodeExporter commented 9 years ago 
Alright, I think this is fixed. CAP is disabled by default and needs to be 
enabled with setCapEnabled. This means that the CAP LS line isn't sent, which 
means the server isn't going to time you out

Original comment by Lord.Qua...@gmail.com on 6 Jan 2013 at 8:21

GoogleCodeExporter commented 9 years ago 
LordQuackstar, might want to check the last two jenkins build's status.

Original comment by entityreborn on 6 Jan 2013 at 8:23

GoogleCodeExporter commented 9 years ago 
Thank you very much gentlemen

Original comment by BranicY...@live.co.uk on 6 Jan 2013 at 9:36