as the script isn't working at all: I get 5 errors per 1 edit
Jun 11 2017
May 8 2017
Mar 5 2017
Dec 18 2016
Mar 5 2016
Jan 9 2016
Jan 6 2016
Nov 23 2015
Sep 24 2015
May 31 2015
May 26 2015
May 2 2015
Apr 30 2015
Now we have piwik installation on our site and are ready for its setup on ru.wikimedia.org:
Apr 26 2015
Oops, I have already deleted it.
Apr 20 2015
Apr 19 2015
@XZise if you want, I can temporary give you autopatrolled or bot rights in ru.wiki and you can try to run the reflinks.py there... I tried to run the bot from another set of articles - the same decoding error appears in other articles, too.
Some more output about the unicode crash:
Apr 18 2015
I updated the bot to the latest revision (but not changed anything in reflinks.py in your post about badtoken recovery), the crash reports are the following.
Apr 9 2015
That's the response of the chapter's director and it's our common practice: when one has no objections, he writes nothing to the list.
Yep, I am the member of the chapter...
Apr 7 2015
Hi Rubin, WMHU has an agreement with the foundation to do so. This is the big thing, you need to get legal approval, neither Peter or I can give that. I'll try and poke Stephen Laporte today to take a look here.
Apr 5 2015
The output is quite huge, so I am posting parts of it:
Apr 4 2015
When you actually mean traceback then yeah please post it because that is the most helpful information for bug reports. In fact you always should include it in any bug report (not only with pywikibot but for all software which shows you a traceback/stack trace).
If you just mean the log, well it could be also helpful as I have no idea what could cause that and maybe that would clear things up. It's very hard to fix something when the description of the bug is very vague and it's not a common bug. Just check through the log that it doesn't accidentally contain sensitive information (like passwords).
Yes, the error about ipadress backport is shown every edit...
Apr 3 2015
I started the bot with -debug option, the same output is shown but one warning message is added now:
The same issue happened today: I ran the bot with extended memory limit up to 4096M as I thought it could be issue.
Apr 1 2015
Mar 14 2015
Why do you need to use CentralNotice rather than plain old sitenotices? The purpose of CentralNotice is to display a [[MediaWiki:Sitenotice]] (on a schedule, across multiple wikis, etc.).
Mar 10 2015
So theoretical steps would be here:
- Receive feedback whether extension could/would be installed
- Set up Piwik instance itself
- Actually deploy/enable extension
Mar 9 2015
Frankly speaking, not yet. But we'll add it to http://wikimedia.ru (our prior official website where we host fundraising system) and that won't be a problem if the extension addition itself is approved.
As a comment - for example, it's used on WM-DE website though the site itself isn't located on WMF servers:
Feb 23 2015
Feb 22 2015
Seems to be fixed now.
Feb 15 2015
It seems that it won't be able to reproduce bug now as the new list was generated and this article disappeared...
Feb 13 2015
Thanks for taking the time to report this!
- Are there more examples for this (as you wrote "articles" in the task summary) or just this one?
- Do you plan to fix this, as you set the "MW-1.25-release" milestone project on this task?
Feb 12 2015
Feb 5 2015
Jan 26 2015
If it is possible, I will send you a set of tracebacks with errors in other articles a couple of week later - I am on the business trip now with no access to Labs...
I'll copy the exact command, too.
Jan 11 2015
Jan 10 2015
Dec 16 2014
I thought that "always" relates to edits, not deletions, as "-help" says about replacements, not deletions:
Not for me.
Dec 15 2014
Seems that we succeed in Scriber situation: I created him an account "Scriber" in one of WMF wikis, where he never logged before and where I can push "ignore similar existing names" option and sent autogenerated password to him.