Joining Channel fails, can't send messages #709
Labels
Comments
|
If possible, could you try build the application from main branch? I have a feeling this is fixed with CASEMAPPING which recently was merged, but not yet released. |
|
This seems to have worked, but every message sent by me is shown twice. Checking with another client this seems to be a display bug, cause on the other client I see the message only once. Messages from other users are also only displayed once. log: e: if i connect thru soju to the same channel, this behaviour does not appear |
|
I am assuming that duplicate messages means both copies of the same message have the same timestamp, correct? If possible, can you clear your history (move/delete |
|
Yes, both have the same timestamp. I moved the history folder and the issue persists. I'm connected to the same channel thru a bouncer aswell this time, in case that is relevant. The first time I wasn't. |
|
Having the same issue with the build I built myself from the main branch, wasn't always there but started happening coincidentally tonight. I am not using a bouncer though. |
|
Unfortunately I'm having trouble recreating duplicated sent messages; connecting to DejaToons, I'm only seeing messages appear once. Can I bother one of you to provide a log with trace logging turned on (by setting the environment variable |
|
Something interesting happend, i could reliable reproduce it, until it somehow stopped (w/o changing anything). It stopped after I joined channel #abc and didn't occur afterwards again, even in #test. I attached a log with only my name, nickserv pass and initial hostmask removed: (I want to point out that the message at 11:01:30.032 and 11:01:30.611 are me typing abc twice back to back to see if i could trigger it again. each message showed only once) how the duplicate messages look: |
|
I can reproduce this again by setting my system clock to 10:15. It does not seem to happen after 11:00AM. I assume there's some time it start happening again. |
|
I think this might be some kind of timing issue, tho I have no idea why it fixed itself magically at 11:00 AM. My clock was always set to automatic by windows (before I started testing here):
|
|
Thank you for following up with all the details. |
|
Thank you for the new logs with the issue recreated! I have a suspicion about what is happening, but I forgot that some logging updates I was counting on to help verify my hunch have not yet made it into |
|
Sure, I can't reproduce it normally anymore (it seem to have temporarily fixed itself?), but changing the pc clock still works. The message do not have the same second timestamp (infact they have quite the drift):
|
|
You know what, it seems to have fixed itself on my client too! How odd is that, we've started experiencing it at the same time and it also disappeared at the same time? It's a proper mystery! |
|
Looks like what I was suspecting, the time recorded locally for the message is too far before the time the server records (preventing the local message from being considered for de-duplication). I'd guess it fixed itself at 11am because that's when your local time was synced with a time server, but the why of it is not particularly important. This should be fixable :) |
Merged
|
Related to the same issue, but this comes with other strange consequences: Amos is a bot that responds to s/x/y prompts. The order of the last two messages should be obviously the other way around. I'll try to figure out what causes this drift on my machine, I just wanted to note it down here for future reference. |
|
To be clear, my guess is that 11am is when your machine synced its time, but from the info available I don't know for sure which machine's clock is off. It could be your local clock, or it could be the server's clock. I'd suggest comparing your local clock against some time server (e.g. NIST). It's also possible that I'm overlooking another reason for the timestamps to be off, but the server's timestamp being before yours eliminates a number of other possibilities. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I tried to join a channel on a network on irc.dejatoons.net. When I enter the join command nothing happens, apart from a message in the server buffer:
There channel doesn't get attached to the sidebar. The log says:
When I click the channel in the UI (i.e. click on #snip) it shows the channel, but fails to load the topic and shows 0 users in there. Even tho I'm sure it has users in it and a topic. It shows the previous scrollback for the channel. It also does not allow me to send messages to the channel.
when I try to part I get a similar error:
I can reliably reproduce this.
complete log:
config used:
I had a similar issue on a different network once, I'll see if I can replicate it there later.
The text was updated successfully, but these errors were encountered: