Closed DoumanAsh closed 10 years ago
Also i looked into some commits before 1.16 release. I'm a bit noob with java and IRC protocol so i'm not seeing much but there is some strange line in commit: 662300ddd83ce9afd7174f4e6ad94c7c6ced2117
LatchingValue
hasDoneAutorun = new LatchingValue (true,false);
Isn't it supposed to be part of onConnect()? Sorry in case if i got it wrong but i have no idea of java at all :D
Please update to 1.18 -- You are encountering a CAP bug that affected some people.
On Fri, Sep 26, 2014 at 7:07 AM, Douman notifications@github.com wrote:
Also i looked into some commits before 1.16 release. I'm a bit noob with java and IRC protocol so i'm not seeing much but there is some strange line in commit: 662300d https://github.com/indrora/Atomic/commit/662300ddd83ce9afd7174f4e6ad94c7c6ced2117
LatchingValue hasDoneAutorun = new LatchingValue(true,false);
Isn't it supposed to be part of onConnect()?
— Reply to this email directly or view it on GitHub https://github.com/indrora/Atomic/issues/55#issuecomment-56958656.
I have this problem on 1.18.... :(
Interesting. I will have to test this.
Glad to see that this is fixed. Will be waiting for new build
With the same settings i can connect to irc.rizon.net just fine on 1.15. Later versions ain't able to connect. Each time registration timeout is happening after atomic has connected to rizon. I haven't tried any other servers as i have no need for them...
host: irc.rizon.net port: 6667
Were there any changes related to connection/registration procedure in atomic?
more detailed: Clear or upgraded install of 1.18: Log: Found your hostname (cached) Checking Ident No Ident response
Then: ERROR :Closing link: -my host name- (Registration time out)
P.s. atomic is very good client