Page MenuHomePhabricator

Lsj (Lsj)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Thursday

  • Clear sailing ahead.

User Details

User Since
Jan 22 2016, 10:35 AM (182 w, 3 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Lsj [ Global Accounts ]

Recent Activity

Jan 29 2016

Lsj added a comment to T124252: NEED_TOKEN error spike when 1.27-wmf.11 SessionManager was deployed to group1.

@Anomie: So where is it appropriate to comment on these errors? In any case, my bot IS coded to retry on the usual kinds of single transient errors that do occur every now and then. That's not what I'm talking about here.

Jan 29 2016, 7:28 PM · MW-1.27-release (WMF-deploy-2016-01-19_(1.27.0-wmf.11)), Reading-Infrastructure-Team-Backlog, Wikimedia-production-error, MW-1.27-release-notes, Patch-For-Review, MediaWiki-Authentication-and-authorization
Lsj added a comment to T124252: NEED_TOKEN error spike when 1.27-wmf.11 SessionManager was deployed to group1.

I started four bot tasks last night. Three of them, running on the same computer, failed at the same time with an Invalid Token error. The fourth one, on a different computer, is still running.

Jan 29 2016, 5:27 PM · MW-1.27-release (WMF-deploy-2016-01-19_(1.27.0-wmf.11)), Reading-Infrastructure-Team-Backlog, Wikimedia-production-error, MW-1.27-release-notes, Patch-For-Review, MediaWiki-Authentication-and-authorization
Lsj added a comment to T124252: NEED_TOKEN error spike when 1.27-wmf.11 SessionManager was deployed to group1.

I started four bot tasks last night. Three of them, running on the same computer, failed at the same time with an Invalid Token error. The fourth one, on a different computer, is still running.

Jan 29 2016, 6:33 AM · MW-1.27-release (WMF-deploy-2016-01-19_(1.27.0-wmf.11)), Reading-Infrastructure-Team-Backlog, Wikimedia-production-error, MW-1.27-release-notes, Patch-For-Review, MediaWiki-Authentication-and-authorization

Jan 28 2016

Lsj added a comment to T124252: NEED_TOKEN error spike when 1.27-wmf.11 SessionManager was deployed to group1.

Login works well enough now, but bot sessions are much less stable than they used to be. Far too often, the bot either gets logged out or starts receiving error messages in the middle of a run. The most frequent error is "Invalid token", but I have also seen messages saying that "The Wiki is currently in read-only mode". If I break the run and start over, everything works fine again.

Jan 28 2016, 9:42 PM · MW-1.27-release (WMF-deploy-2016-01-19_(1.27.0-wmf.11)), Reading-Infrastructure-Team-Backlog, Wikimedia-production-error, MW-1.27-release-notes, Patch-For-Review, MediaWiki-Authentication-and-authorization

Jan 22 2016

Lsj added a comment to T124252: NEED_TOKEN error spike when 1.27-wmf.11 SessionManager was deployed to group1.

Thank you @Anomie. Now it works. Though it does seem like a kluge to have to purge the "deleted" cookies "by hand" in the code.

Jan 22 2016, 8:04 PM · MW-1.27-release (WMF-deploy-2016-01-19_(1.27.0-wmf.11)), Reading-Infrastructure-Team-Backlog, Wikimedia-production-error, MW-1.27-release-notes, Patch-For-Review, MediaWiki-Authentication-and-authorization
Lsj added a comment to T124252: NEED_TOKEN error spike when 1.27-wmf.11 SessionManager was deployed to group1.

I'm getting this error since last night, when trying to login through DotNetWikiBot 3.14. Any suggestions on how to get around it?

Jan 22 2016, 11:05 AM · MW-1.27-release (WMF-deploy-2016-01-19_(1.27.0-wmf.11)), Reading-Infrastructure-Team-Backlog, Wikimedia-production-error, MW-1.27-release-notes, Patch-For-Review, MediaWiki-Authentication-and-authorization