[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Weechat-dev] [bug #38215] Weechat relay sync/desync not working as spec

From: anonymous
Subject: [Weechat-dev] [bug #38215] Weechat relay sync/desync not working as specified
Date: Thu, 31 Jan 2013 23:52:08 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.11 (KHTML, like Gecko) Ubuntu/12.04 Chromium/20.0.1132.47 Chrome/20.0.1132.47 Safari/536.11


                 Summary: Weechat relay sync/desync not working as specified
                 Project: WeeChat
            Submitted by: None
            Submitted on: Thu 31 Jan 2013 11:52:07 PM UTC
                Category: relay plugin
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Keith Johnson
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
                IRC nick: ubergeek42



See attached screenshot.

I have modified my client slightly, and it calls desync and desync *
buffer,nicklist when it connects(To attempt to narrow down this bug)

Everything works as expected, I don't receive any _nicklist messages from
weechat.  Then I sync on a single channel(freenode.#ubergeek42, a test channel
I use), but get the nicklist notifications for other channels that I am in.  

Additionally, I sent a message in my test channel(#ubergeek42) while this
client was connected, and no message was sent to the client.  I believe it has
only worked for me when calling 'sync' with no arguments to sync everything.

Looking at the code I don't see anywhere in the
relay_weechat_protocol_*_nicklist_cb that it checks the buffers_sync variable
to see if it should send this nicklist.  The other issue of not sending
messages for a 'sync'd buffer is more unusual, as that code appears to check
the hashtable, but for some reason it isn't working(maybe the format for full
buffer name is incorrect)?

This was tested with version 0.4.0-dev(compiled Nov 9th).


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]