Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add method to fetch the current lag from the Wikibase instance #470

Merged
merged 3 commits into from
Jun 26, 2020

Conversation

wetneb
Copy link
Member

@wetneb wetneb commented Dec 11, 2019

Initially designed for #469, closes #510.

@coveralls
Copy link

coveralls commented Dec 11, 2019

Coverage Status

Coverage decreased (-0.02%) to 84.788% when pulling 73910ab on issue-469-continuous-throttling into 6cb761d on master.

@wetneb
Copy link
Member Author

wetneb commented Jun 25, 2020

Since there is no established guidance from WMDE about how bots should be throttled, I am removing the throttling logic to keep only the change which makes it possible to retrieve the current maxlag.

Therefore this PR can be merged as a fix for #510.

@wetneb wetneb marked this pull request as ready for review June 25, 2020 16:07
@wetneb wetneb requested a review from Tpt June 25, 2020 16:07
@wetneb wetneb force-pushed the issue-469-continuous-throttling branch from 3adab4a to cec3657 Compare June 25, 2020 16:20
@wetneb wetneb changed the title Continuous throttling policy based on MediaWiki's lag Add method to fetch the current lag from the Wikibase instance Jun 26, 2020
@wetneb wetneb merged commit cde4f66 into master Jun 26, 2020
@wetneb wetneb deleted the issue-469-continuous-throttling branch June 26, 2020 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Access current maxlag value of the server
3 participants