Xqt created this task.
Xqt added a subscriber: Xqt.
Xqt added projects: Pywikibot-Cosmetic-changes, pywikibot-core.
Restricted Application added subscribers: Aklapper, pywikipedia-bugs.
TASK DESCRIPTION
```
>>> Xj 600 S <<<
Links to: [[Yamaha XJ 600 S/N Diversion]].
Links to: [[Yamaha XJ600S/N Diversion]].
Exception in thread Put-Thread:
Traceback (most recent call last):
File "C:\Python27\lib\threading.py", line 551, in __bootstrap_inner
self.run()
File "C:\Python27\lib\threading.py", line 504, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\pwb\core\pywikibot\__init__.py", line 715, in async_manager
request(*args, **kwargs)
File "C:\pwb\core\pywikibot\page.py", line 1044, in _save
comment = self._cosmetic_changes_hook(comment) or comment
File "C:\pwb\core\pywikibot\page.py", line 1094, in _cosmetic_changes_hook
self.text = ccToolkit.change(old)
File "C:\pwb\core\scripts\cosmetic_changes.py", line 238, in change
new_text = self._change(text)
File "C:\pwb\core\scripts\cosmetic_changes.py", line 231, in _change
text = self.safe_execute(method, text)
File "C:\pwb\core\scripts\cosmetic_changes.py", line 209, in safe_execute
result = method(text)
File "C:\pwb\core\scripts\cosmetic_changes.py", line 657, in replaceDeprecatedTemplates
if self.namespaces[10].case == 'first-letter':
AttributeError: CosmeticChangesToolkit instance has no attribute 'namespaces'
WARNING: Configuration variable 'account_global' is defined but unknown.
Misspelled?
WARNING: Configuration variable 'use_diskcache' is defined but unknown.
Misspelled?
WARNING: Configuration variable 'notify_unflagged_bot' is defined but unknown.
Misspelled?
Pywikibot: pywikibot-core (e896511, s6206, 2015/02/26, 18:26:26, ok)
Release version: 2.0b3
httplib2 version: 0.9
cacerts: C:\pwb\core\externals\httplib2\python2\httplib2\cacerts.txt
certificate test: ok
Python: 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)]
unicode test: ok
PYWIKIBOT2_DIR: Not set
PYWIKIBOT2_DIR_PWB: C:\pwb\core
PYWIKIBOT2_NO_USER_CONFIG: Not set
Config base dir: C:\pwb\core
C:\pwb\core>
```
TASK DETAIL
https://phabricator.wikimedia.org/T91234
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: Xqt
Cc: pywikipedia-bugs, Xqt, Aklapper, jayvdb
Jsalsman added a comment.
@Halfak, I see now that mediawiki-utilities has all the bot features needed, and I don't see anything in pywikibot upon which anything here depends, so since mediawiki-utilities has the better text age and attribution, I suppose dependencies on pywikibot ought to be removed.
TASK DETAIL
https://phabricator.wikimedia.org/T89416
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: Jsalsman
Cc: Rits, Halfak, NiharikaKohli, Evanontario, jayvdb, Qgil, Bawolff, Aklapper, Jsalsman, pywikipedia-bugs
Jsalsman added a comment.
@bawolff, I don't understand what you mean by "stakeholders." The goal is to create a bot which assists in identifying out-of-date, inaccurate, and confusing content, packaging excerpts of those passages for review, accepting reviewers' responses for whether and how the passages should be updated, and tabulating those responses. It's intended to be used on any wiki in any language which is facing out-of-date content issues. Is it appropriate to have a conversation with the people who might benefit from such a bot before it's been implemented and some semblance of measurements have been made on its capability, utility, and requirements for production use? What would the topics of such a conversation entail?
TASK DETAIL
https://phabricator.wikimedia.org/T89416
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: Jsalsman
Cc: Rits, Halfak, NiharikaKohli, Evanontario, jayvdb, Qgil, Bawolff, Aklapper, Jsalsman, pywikipedia-bugs
Bawolff added a comment.
I cant speak for qgil, but i have similar concerns. I dont think a formal poll is necessary (or even a good idea at this stage). What i would like to see is a list of stakeholders identified (at least people who would be affected by the planned first deployment of such a feature. The feature is generic so there could be many other stakeholders eventually, but initially there will be some group you presumably plan to target first). I would like to see a conversation with some people in this group (e.g. at a VP if they are wikipedians. If your target is a wmf wiki, the discussion should preferably be on wiki as mailing lists are not populated by the average user) that indicates that at least some members have thought about the idea and think it would be a net positive for them or their project.
Imho anyways. Qgil may have different opinions on what is needed and his opinion is what counts.
TASK DETAIL
https://phabricator.wikimedia.org/T89416
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: Bawolff
Cc: Rits, Halfak, NiharikaKohli, Evanontario, jayvdb, Qgil, Bawolff, Aklapper, Jsalsman, pywikipedia-bugs
despens added a comment.
Apparently, `normalizePageName` in `MediaWikiSite` doesn't follow redirects. `MediaWikiSite` writes this error log:
2015-03-03 23:42:47 catalog wiki: call to <//catalog.rhizome.org/api.php?action=query&prop=info&redirects=1&converttitles=1&format=json&titles=Delocator.net> returned bad json: <html>
<head>
<title>Security redirect</title>
</head>
<body>
<h1>Security redirect</h1>
<p>
We can't serve non-HTML content from the URL you have requested, because
Internet Explorer would interpret it as an incorrect and potentially dangerous
content type.</p>
<p>Instead, please use <a href="https://catalog.rhizome.org/api.php?action=query&prop=info&redirect…">this URL</a>, which is the same as the
URL you have requested, except that "&*" is appended. This prevents Internet
Explorer from seeing a bogus file extension.
</p>
</body>
</html>
When appending `&:*` to the original API request in `includes/site/MediaWikiSite.php:136`, like this:
$url = wfAppendQuery( $this->getFileUrl( 'api.php' ), $args ). '&*';
the request works and `normalizePageName` returns a valid page name.
TASK DETAIL
https://phabricator.wikimedia.org/T91439
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: despens
Cc: pywikipedia-bugs, Aklapper, despens, Wikidata-bugs, jayvdb, Anomie, Legoktm