You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
serviceTopicQueue calls upsertMatrixRoom to store the updated topic in the datastore.
In the Nedb implementation this calls matrix-appservice-bridge's RoomStore.setMatrixRoom, which stores it keyed on id: matrixRoom.getId(), with properties id, matrix_id, matrix.
On future topic changes, getEntriesByRemoteId instead returns the entry for id $matrixRoomId $network $channel, as that has a remote_id of $network $channel, which has no topic set in the MatrixRoom data.
Unsure if this is a bug in matrix-appservice-irc or matrix-appservice-bridge (or both), feel free to transfer this issue if needed.
The text was updated successfully, but these errors were encountered:
serviceTopicQueue
callsupsertMatrixRoom
to store the updated topic in the datastore.In the Nedb implementation this calls matrix-appservice-bridge's
RoomStore.setMatrixRoom
, which stores it keyed onid: matrixRoom.getId()
, with properties id, matrix_id, matrix.On future topic changes,
getEntriesByRemoteId
instead returns the entry for id$matrixRoomId $network $channel
, as that has aremote_id
of$network $channel
, which has notopic
set in the MatrixRoom data.Unsure if this is a bug in matrix-appservice-irc or matrix-appservice-bridge (or both), feel free to transfer this issue if needed.
The text was updated successfully, but these errors were encountered: