Does'nt send chat to ADC hubs

[Lord Squeak 0]

b5, Doesn't send any chat messages to ADC hubs. (and its been like this since alpha went public, bug reported twice)

Checking with the CDM , it realy doesnt send anything ,, at all to ADC hubs.

old hubs works just fine.

[Crise 26]

Mine works with ADC just fine, I need a specific test case

[Zlobomir 3]

Is it ONLY with DSHub?

[Lord Squeak 0]

As far as I could tell , It logs on ok.

but after that the client doesn't send anything to the hub at all.

(atleast nothing that shows up in the CDM Debug)

it was the same with the 2 previous betas.

The b4 version worked fine for me , until it got disabled.

I'm on 0.4.0 now , so I can't do anymore tests.

Mine works with ADC just fine, I need a specific test case

Could you be more specific?

[Crise 26]

specific test case, means a hub where I can reproduce this.... (ie. a hub where this happens to you all/most of the time)

[Lord Squeak 0]

well , I just installed the latest DSHUB which supports adc1.0 , tested on all 3 hubs im hosting

adc://audiophile.no-ip.org:48000

adc://akibamarket.no-ip.org:777

adc://yakuza.otaku-anime.net:555

Also tested a DCWatch hub adc://adcpirre.no-ip.info:443

And an ADCH++ hub adc://elite.4242.hu:2424

In fact , I can't find it working on any adc hubs at all.

nmdc hubs works just fine though.

[Crise 26]

First hub on the list od dshubs:

[17:29:09] <Crise> adc chat test

[17:29:25] <Crise> works fine as far as I can see

On the ADCH:

[17:31:54] <Crise> adc chat test

[17:32:05] <Crise> working fine as far as I can see

and just to make it clear:

Hub: [Outgoing][195.228.***.***:2424] BMSG **** 2nd\stest

Hub: [incoming][195.228.***.***:2424] BMSG **** 2nd\stest

[Lord Squeak 0]

Well done. that's the most elaborate bug testing I have ever seen. I guess the bug is fixed now.

[Satan 1]

What do you expect him to do? Have a 5 hour conversation?

If you expect us to believe that it works for the first 2 lines you type then all of a sudden stops working, your deluded (or insane) if you dont give us an explanation of how and when it supposedly stops working, how can we test it?

[Crise 26]

Well done. that's the most elaborate bug testing I have ever seen. I guess the bug is fixed now.

I don't know if that was a sarcastic comment or not, but the way I tested it wasn't elaborate at all... because it only proves that ADC chat works for me and nothing more... what I mean is that what works for me doesn't necessarily have to work for you.

But as Satan said, with what you gave us... this is about all we can do.

[YouKnowWho 0]

Works for me as well in my ADC hubs, no problems in chat.

[Lord Squeak 0]

What do you expect him to do? Have a 5 hour conversation?

If you expect us to believe that it works for the first 2 lines you type then all of a sudden stops working, your deluded (or insane) if you dont give us an explanation of how and when it supposedly stops working, how can we test it?

first 2 lines? ,, where did you get that from? (talk about deluded), I never said it works for 2 lines.

It does not work at all.

And pardon me for being sarcastic, but this is only the 3rd time I've reported this bug.

and only the first time someone even showed any interest in in the bug.

and with that amazing bug testing "It works for me.",,,

Well , Anyhow.

as I've said earlier (either in this post or in the other 2 bug reports),,

Chatting does not work at all, in any adc hubs at all.

Checking the CDM Debug, the client is not sending anything at all. (while nmdc hubs works fine)

It haven't worked at all since the b4 client. (b4 and 0.4.0 works fine)

And that is ALL I can tell you.

Now, If there is any more info I could supply, or test that I can do, that might help you track down the bug, then please tell.

[Pothead 0]

What DC++ core / svn build is this version of apex built on ?

Lord Squeak, could you test with 0.704, and the version of StrongDC which this is built from, to see if it's an inherited bug, or an apex one ? :)

[Lord Squeak 0]

Works fine with DC++ 0.704 and StrongDC 2.12

mind , this bug only affects me with the b5 version, the b4 version worked fine.

[mcravener 0]

mind , this bug only affects me with the b5 version, the b4 version worked fine.

Isn't this all a bit academic since the Bug report is supposed to be about the latest client:

Bug report rule 4: Please also ensure that you are using the latest ApexDC++ version"

Hmmmm? :)

[Zlobomir 3]

Well, in this case it helps to determine the bug by tracking the changes made in the code b/w versions.

[Lord Squeak 0]

Isn't this all a bit academic since the Bug report is supposed to be about the latest client:

Bug report rule 4: Please also ensure that you are using the latest ApexDC++ version"

Hmmmm?

well , this bug has been persistent since the first b5 came out , and is still there.

I might add here that I managed to kindah fix it.

first I made a completely clean install of it and it worked.

then I copied files over to the clean install until it stopped working.

The problem seems to be located somewhere in the settings .xml file.

So i started removing chunks of settings until it worked again.

As i recall, it started working after removing all the font settings and some other stuff near it , then when i started placing settings back into the file it froze on startup , and somewhere along the line there it started working again.

To make a totaly wild guess at whats causing the bug, I'd say It didnt like my old font settings, because ADC uses unicode, so it just goes for a beer and sandwich while i was typing.