coren added a comment. It's pretty clear that any tool that aims for reliability necessarily //must// have the ability to reconnect if the connection is dropped between transactions. It's not clear that values much over 60s are useful (any limit will end up being a problem if the code doesn't reconnect) but I could see 120s as a reasonable compromise to cover cases where a bit of unplanned sluggishness causes intermittent issues.
All of that said, a tool that breaks because it does not have error handling to recover from a connection to the DB being disconnected can never expect to be stable or reliable in the long term and needs to be fixed. TASK DETAIL https://phabricator.wikimedia.org/T76699 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Springle, coren Cc: Betacommand, Multichill, Giftpflanze, Lokal_Profil, Steinsplitter, Husky, Springle, Magnus, Aklapper, coren, Danilo, Wikidata-bugs, aude, jayvdb, scfc _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
