To-Do/RandomBugs

From Tel'Laerad Wiki

This is a list of random bugs that have occurred for no apparent reason, which disappeared completely without being tracked down, for future usage should they occur again, or something related be seen. Without them recurring, they cannot be debugged, as the problem isn't there. That said, they need to be noted as having happened once before in such and such circumstances, in case they occur again and can be tracked down.

Many of these were likely a one-off issue and should not happen again, or recur infrequently enough that they evade debugging, and may be gone through general updates. This list shouldn't be treated as an 'outstanding bug' list and these should not bother users. We do already have one of those, for confirmed bugs, on the main To-Do page. Any users who encounter any of these bugs are requested to contact staff with all the information they can provide on events.

Standing instructions should one of these bugs reoccur is to get debug logs of the bug occurring, as instructed in the appropriate document in our Technical Documents forum, THEN 'fix' the problem, wherever possible. Allowing user disruption to continue shortly to get new information which may allow bugs to be forever excised (and thus providing better service for the future) is the norm outside of major events, during which a 'workaround' or an action to mitigate the bug may be taken before logs are collected. New information is the only way that any of these which do occur again can be stopped from occurring a third time, and so on.

• Deathsplit bug STILL EXISTS. We thought we had perhaps seen the last of it. After connection issues to Valhalla apparantly, the network refused to relink. Debug information was not collected. We can only hope to find it another time and stop it. The previous suspected cause being changed in InspIRCd did not stop it.
• Usermodes on oper appear to fail to synchronise correctly; our BOPMs are randomly +B or not +B on different servers. This does not cause any terrible behaviour, so it is not a huge priority, but could result in Bad Things.
• Mibbit + Cloaking + Non-Resolving IP resulted in an uncloaked IP with +x at least once. If this is reproducible every time this arrangement occurs, needs to be filed on the main page and with the Insp people.
• Channel mode +r missing from a channel.

Recurring Random Bugs

• Services: At least two people have gotten "Internal error - unable to process request." upon trying to identify. Went away upon service restart one time, went away when the person disconnected and reconnected the next time. (I heard a rumour that this relates to multiple users from the same host, perhaps? ~Namegduf