matej_suchanek added a comment.

  I was suspicious there could be a race condition since my bot uses the 
asynchronous saving feature. So, I forced it to save synchronously. When I have 
it log out before running the script, I get messages like
  
    Change summary: add missing labels
    Logging in to wikidata:wikidata as MatSuBot@[redacted bot password key]
    WARNING: API warning (main): Subscribe to the mediawiki-api-announce 
mailing list at 
<https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/>
 for notice of API deprecations and breaking changes. Use 
[[Special:ApiFeatureUsage]] to see usage of deprecated features by your 
application.
    WARNING: API warning (login): Fetching a token via "action=login" is 
deprecated. Use "action=query&meta=tokens&type=login" instead.
    ERROR: Received incorrect login token. Forcing re-login.
    Change summary: add missing labels
    ERROR: User assertion failed. Forcing re-login.
    Change summary: add missing labels
    ERROR: User assertion failed. Forcing re-login.
    Change summary: add missing labels
  
  and so on. The `ERROR:` lines later occur less often. But the script **keeps 
running**, and edits are saved.
  
  So there are two problems:
  
  - the bot does not handle and retry in asynchronous mode (but it does in 
synchronous mode)
  - there are still some login (edit token) problems
  
  The doi links problem could be related, but I get errors by running the bot 
on Wikidata.

TASK DETAIL
  https://phabricator.wikimedia.org/T343187

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: matej_suchanek
Cc: mykhal, dimka, Xqt, Aklapper, matej_suchanek, pywikibot-bugs-list, mevo, 
PotsdamLamb, Jyoo1011, JohnsonLee01, SHEKH, Dijkstra, Khutuck, Zkhalido, 
Viztor, Wenyi, Tbscho, MayS, Mdupont, JJMC89, Dvorapa, Altostratus, 
Avicennasis, mys_721tx, jayvdb, Masti, Alchimista
_______________________________________________
pywikibot-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to