| valhallasw added a comment. |
I think using the maxlag data is fundamentally incorrect: having N seconds lag does not imply that the lag will be resolved in N seconds: if there are no edits, the replag will likely be resolved much quicker, and if there is massive congestion, it could take much longer.
From the api docs: https://www.mediawiki.org/wiki/Manual:Maxlag_parameter
The following HTTP headers are set:
Retry-After: a recommended minimum number of seconds that the client should wait before retrying
X-Database-Lag: The number of seconds of lag of the most lagged slave
So we should just follow the Retry-After header instead.
TASK DETAIL
EMAIL PREFERENCES
To: valhallasw
Cc: Xqt, jayvdb, valhallasw, Aklapper, pywikibot-bugs-list, Multichill, Sethakill, Mdupont, JJMC89, dg711, Anomie, Legoktm
Cc: Xqt, jayvdb, valhallasw, Aklapper, pywikibot-bugs-list, Multichill, Sethakill, Mdupont, JJMC89, dg711, Anomie, Legoktm
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
