Ricordisamoa changed the task status from "Open" to "Stalled".
Ricordisamoa placed this task up for grabs.
Ricordisamoa set Security to None.
TASK DETAIL
https://phabricator.wikimedia.org/T70898
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: Ricordisamoa
Cc: Legoktm, jayvdb, Ricordisamoa, pywikipedia-bugs
jayvdb added a comment.
I believe this has more than enough scope to be a 3-month GSoC project, esp. if copious unit tests are written.
I am willing to write this up as a project, if a flow developer can be a co-mentor to
1. review the *design* of the new pywikibot classes, which would need to reflect design decisions of Flow, some of which may not be exposed via the flow API, and
2. help with reviewing test cases and debugging any problems.
TASK DETAIL
https://phabricator.wikimedia.org/T67119
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: jayvdb
Cc: NiharikaKohli, Capt_Swing, Qgil, jayvdb, Mattflaschen, Xqt, Ricordisamoa, Multichill, Ladsgroup, matthiasmullie, Gryllida, EBernhardson, Spage, Quiddity, pywikipedia-bugs
jayvdb created this task.
jayvdb added subscribers: jayvdb, Aklapper.
jayvdb added a project: pywikibot-core.
Restricted Application added a subscriber: pywikipedia-bugs.
TASK DESCRIPTION
API request 'help' fails as of 1.25 (T93186)
```
>>> import pywikibot
>>> enwp = pywikibot.Site('en', 'wikipedia')
>>> r = pywikibot.data.api.Request(site=enwp, action='help', modules='help')
>>> r.submit()
Non-JSON response received from server wikipedia:en; the server may be down.
...
```
TASK DETAIL
https://phabricator.wikimedia.org/T93188
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: jayvdb
Cc: Aklapper, jayvdb, pywikipedia-bugs
jayvdb created this task.
jayvdb added a subscriber: jayvdb.
jayvdb added projects: pywikibot-core, Pywikibot-tests.
Restricted Application added subscribers: Aklapper, pywikipedia-bugs.
TASK DESCRIPTION
In the test suite, TestRequest and DryRequest replace the original Request class as required, however any call to CachedRequest bypasses these alternative implementations.
The constructor of CachedRequest accepts an extra 'expiry' parameter at the first position which does not appear in the super class Request.
TestRequest subclasses CachedRequest, but doesnt use the parent classes constructor signature, as doesnt have an 'expiry' - instead it has a hard-coded expiry.
The simplest approach is to create TestCachedRequest which matches the constructor signature of CachedRequest, and replaces CachedRequest in the test suite. (and do the same for DryRequest)
Another approach to unravel this mess is to move the CachedRequest expiry parameter to a named keyword parameter which is mandatory/has a default (similar to 'site'), which would require a funky decorator to deprecate calling CachedRequest with a literal number as the first parameter.
Then TestRequest and DryRequest can be used as a replacement for CachedRequest, and would simply ignore the 'expiry' parameter if it exists.
TASK DETAIL
https://phabricator.wikimedia.org/T93175
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: jayvdb
Cc: pywikipedia-bugs, jayvdb, Aklapper
Sampadmedda added a comment.
@Qgil, @Ricordisamoa , I have made my final draft and there would be no further changes from my side unless and until asked specifically by the members or mentors.
Please do understand that I am new to phabricator and wanted my proposal to be as much complete as possible.
This is my first attempt at GSOC and even though I know that good Content speaks all , I just don't want to leave any stone unturned. I was actually learning from other proposals and incorporating the necessary edits.
Now, this is the final edit from my side.
Thank you for understanding.
TASK DETAIL
https://phabricator.wikimedia.org/T93060
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: Sampadmedda
Cc: XZise, NiharikaKohli, MZMcBride, Ricordisamoa, Qgil, Aklapper, Sampadmedda, Imaculate, pywikipedia-bugs
Qgil added a comment.
@Sampadmedda, you have edited the description 16 times in 3h30, and you could probably have ended up in the same place by doing those edits locally and then posting one update here. Also, if you need a wiki page to draft your proposal, we can offer you all the wiki page you need under your User page in mediawiki.org.
We have good reasons to think that Phabricator beats mediawiki.org when it comes to present a proposal, gather interest, and drive community discussion. We are asking GSoC students to use one tool in addition to Google Melange to share their proposals publicly, and I don't think requesting them to use three tools to handle their proposals is a better idea.
Then again this is a new process, and you are among the first applicants. Some rough edges are expected. Thank you for your understanding.
TASK DETAIL
https://phabricator.wikimedia.org/T93060
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: Sampadmedda, Qgil
Cc: XZise, NiharikaKohli, MZMcBride, Ricordisamoa, Qgil, Aklapper, Sampadmedda, Imaculate, pywikipedia-bugs