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
Half-Shot opened this issue
May 10, 2023
· 2 comments
Labels
S-MajorSeverely degrades major functionality or product features, with no satisfactory workaroundT-DefectBugs, crashes, hangs, vulnerabilities, or other reported problems.
This seems to be caused by the bridge joined channel list getting out of date, and so when the bridge tries to join #foo while the IRC session is already joined, it fails.
For anyone struggling with this: Send a !reconnect command inside your admin room for the bridge, which should cause the bridge to reconnect to the channels.
A true fix will be provided in due course.
The text was updated successfully, but these errors were encountered:
Half-Shot
added
T-Defect
Bugs, crashes, hangs, vulnerabilities, or other reported problems.
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
labels
May 10, 2023
Doesn't seem to work for me either, any message I send doesn't appear on (OFTC) IRC. Is there any other potential workaround that I can try?
edit: seems to have reconnected at 23:20 that day, so about 9 hours later from making that screenshot. "Downtime" was some hours longer, at most somewhere around 24 hours from being disconnected from IRC
S-MajorSeverely degrades major functionality or product features, with no satisfactory workaroundT-DefectBugs, crashes, hangs, vulnerabilities, or other reported problems.
This seems to be caused by the bridge joined channel list getting out of date, and so when the bridge tries to join
#foo
while the IRC session is already joined, it fails.For anyone struggling with this: Send a
!reconnect
command inside your admin room for the bridge, which should cause the bridge to reconnect to the channels.A true fix will be provided in due course.
The text was updated successfully, but these errors were encountered: