@valhallasw We are trying to break as little as possible. So if anyone's cron automatically updates git and it still runs under py2 (per my experience and per our Wikimedia Hackathon meetup a dominant group of users), this would break their cron scripts. That's why we are trying to freeze the current master (I like the idea of final v3 release anyway) and start a new branch from it.
I thought we would rename old core/master. But that is not possible, right?
I like the idea of making the current master a read-only repository/branch and start a new one. This way the development will be concentrated on one branch only, and there will be no breakage at all. Or if not read-only, then only merge important bug-fixes, but nothing else. The version should be moved to 4.0 surely (the suggested move to SemVer can be done afterwards, no need to block py2 deprecation on this).
Okay, I understand why it does so, but the parameter is "1", not "8", so the IABot does an incorrect thing
The "Harvnb" template itself has been changed and does not contain that leaked part anymore. The same wikitext can be found in templates Coord and Col-begin currently. Anyway, I checked for the leaked wikitext in articles and it seems it does not leak anymore. At least not in the way described here.
Sun, Jun 23
Sat, Jun 22
Wed, Jun 19
Tue, Jun 18
Okay, but by removing format block new infoboxes will be formatted inline, which is not desired (obviously). And by setting a different value the current spaces won't be preserved. There is no such option "block when inserting, but leave as is otherwise". This issue was recently a dispute between bot owners on Czech Wikipedia and we finally agreed on a compromise to adjust our bots to leave the number of initial spaces on each line as is (if block formatting there is not broken of course).
I tried to create a Proof of Concept, see
Okay, now closed (read-only) wikis can be read by any bot. What is still to be solved:
Seems duplicate to T57063
Perhaps similar root cause as in T225861?
Sun, Jun 16
Sat, Jun 15
I see. But I doubt there is no external library, that could handle this.
Fri, Jun 14
We see in our research that newcomers wander around being confused about where to start. We think that the homepage can be a clear place that leads them to the right places for them to get started. That's why we want to make sure all newcomers know about the homepage
Thu, Jun 13
On testwikis this is easy to do, see e.g. https://test.wikipedia.org/wiki/Template:Orphan_file or https://test.wikipedia.org/wiki/Template:No_license or https://test.wikipedia.org/wiki/Wikipedia:Categories_for_discussion/Working
Also on Travis sometimes
What I experienced today on Travis-CI forum (could something similar be achieved by GuidedTour?):
Sure, that's why I marked it WIP a month ago!
Yes, this is an old issue. I sovled it in https://gerrit.wikimedia.org/r/#/c/pywikibot/core/+/429875/ perhaps we could detach the solution out of there too.
@MMiller_WMF Hi, on Hackathon we discussed newcomers should be more aware of the successfully created account.
Wed, Jun 12
Why not create one?
For me, both Python 2 and 3 works the same. Only the read() works just once (as a stream), so better to copy the captured string.
$ python pwb.py shell Welcome to the Pywikibot interactive shell! >>> from tests.utils import execute_pwb tests: max_retries reduced from 15 to 1 >>> import io >>> stream = execute_pwb(['hello'], data_in=chr(3), timeout=6) >>> stderr = io.StringIO(stream['stderr']) >>> print(stderr.read()) ERROR: hello.py not found! Misspelling? NOTE: Starting the most similar script shell.py *** in 5.0 seconds; type CTRL-C to stop. Welcome to the Pywikibot interactive shell!
Tue, Jun 11
I see. I'm not sure I understandcorrectly, where the file would be located, but anyway, this seems doable.
Okay, so remove the warning completely?
Mon, Jun 10
Sometimes I visit a new watchlist entry, the entry becomes seen, but some - already visited - change underneath gets marked as unseen. I click to that change and it is marked as seen, but the first entry is marked as unseen back.
Okay, now only SpamBlacklist and too long pages fixes are needed, thanks @Mh-3110 for your work!
Sat, Jun 8
Fri, Jun 7
Follow-up tasks created already, marking as resolved then
Thu, Jun 6
This seems solved, T47070 is still happening
Wed, Jun 5
The issue is worse if there are two reverts of the same edit conflicting each other, but the authors of the conflicting reverts changed also something else. Thus two reverts of the same edit can silently conflict, which makes ridiculous output (see https://cs.wikipedia.org/w/index.php?title=Jablko&action=history)
Tue, Jun 4
Sat, Jun 1
Is this fixed?
The same with long-running bot tasks. My bot tasks sometimes stops in the middle and asks for password instead of automatic relogging
Fri, May 31
Hi @Mh-3110 , you should preserve the same Change-Id line (Change-Id: Ibbe5afaa3b9511e7370dce6685eea9f0e5952cac) in your commit message in order not to create whole new patch for every small change.
I think there is no need to split the task. Just create patches for individual parts and assign this task to them. Or just create subtasks for those we can not solve right now.
Is this fixed?
If I run python setup.py test on my computer, at one point it asks for password even if I it is already stored in pywikibot.lwp:
We can use BotPasswords to make tests pass, but it would mean we have one password for Beta Cluster wikis, another password for Wikimedia wikis and another password for musicbrainz wiki
Wed, May 29
I can confirm, it is much better than before, but still sometimes leaves visited change marked in bold
( @Xqt: Please don't restart errored builds if not. They are erroring again and it takes them 50 minutes to timeout. The other tests must wait for these to complete. )
Ignoring pytest: markers 'python_full_version < "3.5"' don't match your environment Ignoring pytest: markers 'python_full_version >= "3.5"' don't match your environment Ignoring werkzeug: markers 'python_full_version >= "3.8"' don't match your environment Ignoring mock: markers 'python_version < "3"' don't match your environment
Mon, May 27
musicbrainz issue solved, only the timeout is the issue now (happens only sometimes)
- catfiles: ok, let's leave it as is
- everything seems okay now
May 26 2019
Yeah, this is a standard solution. For nobots, there is a nice botMayEdit function in page.py. I don't know, how to detect SpamBlackList though. The memory issues when saving are still not properly handled in Pywikibot unfortunately.
May 25 2019
The username and general password do match. What else should be set to make it work? OAuth? Some preferences?
May 24 2019
May 23 2019
It works nicely!
May 22 2019
Is this issue also somewhere else?