| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
Previously used an in-memory map to represent the database content and kept those in sync
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These warnings arecompiler annoyances where the vala compiler creates C code
that is usually unexpected in proper C code and thus triggers warnings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Direct chat corrections are accepted by bare JID, but the latest
correction lookup still constrained the query by the original full
resource; a correction sent from another resource therefore produced no
matching correction row, returned -1, and wrote that sentinel into the
message content item's foreign id.
Align the lookup with the acceptance rule: retain occupant id matching
for MUC corrections, retain resource matching for non chat cases where
it is still meaningful, and avoid resource filtering for direct chat
corrections.
|
|
|
|
|
|
|
|
|
|
|
|
It previously triggered the leak checker, even though eventually the widget
would be disposed when the corresponding message skeletion got disposed.
|
|
|
|
|
|
fixes #1822
|
|
|
|
|
|
|
|
|
|
interface
|
|
|
|
|
|
|
|
|
