User Details
- User Since
- Oct 7 2014, 7:43 AM (530 w, 2 d)
- Availability
- Available
- IRC Nick
- kelson
- LDAP User
- Kelson
- MediaWiki User
- Kelson [ Global Accounts ]
Mon, Dec 2
If I give a bit more context about this request, I would invite you to read https://phabricator.wikimedia.org/T349972. In this ticket, the WMF has implemented in the mobile-html output, the original thumbnailing width for use/Kiwix, so we are in position to render the real thumbnail size as given by the wikitext. See https://github.com/openzim/mwoffliner/issues/1925 for the upstream (MWoffliner) ticket.
Mar 5 2024
Dec 17 2023
@abi_ Thank you! Seems to work fine!
Dec 8 2023
Error is in the config file: git@git@github.com:kiwix/apple.git, this is not a valid address.
@abi_ I'm a bit puzzled by the situation. Translatewiki bot has access to the whole Kiwix organisation on Github and have good permissions for the kiwix/apple
Dec 6 2023
Dec 2 2023
@abi_ We are working on it. See https://github.com/kiwix/apple/issues/571. I will come back to you within a few days when this will be done.
Nov 27 2023
Nov 25 2023
Nov 23 2023
Nov 11 2023
Nov 7 2023
@matmarex Thank you very much for this fix!
Oct 30 2023
Yes, this is on the radar, but we face pretty much difficulties around mobile-html new end-point for the moment. So not a TOP prio our side. I honestly don't think we will be able to tackle this before 2024.
Oct 29 2023
No sure what is the exact status here, but on the size of Kiwix we have implemented the support of the new mobile-html REST end-point. Unfortunately we are not really able to create ZIM files because of https://phabricator.wikimedia.org/T349972. We still rely therefore on the mobile-section end-point.
Oct 15 2023
Oct 13 2023
Actually this ticket should be a bug, image resolutions are far too big for a mobile end-point and seems to be a waste of bandwidth. I have open a ticket at https://phabricator.wikimedia.org/T349972
Sep 26 2023
@MatthewVernon That would be welcome on MWoffliner side! For the rest I can not say, but respecting the RFC sounds here quite important.
Aug 27 2023
@ssastry AFAIK what is described seemscorrect to me. @vadim-kovalenko and @cscott would certainly be able to tell more as they both know MWoffliner and the Wikimedia backend infra.
@MSantos Thank you very much
Aug 8 2023
@akosiaris @MSantos May I underline Vadim's request: carifying if we (at Kiwix) can still benefit from the mobile-sections API until we finish with the MWoffliner code update is an important and relatively time-dependant question.
Jun 19 2023
@daniel Thank you! Things are clearer now for me. At the core of my problem is that we have always been using $wgContentNamespaces to know which namespaces should be scraped... and here it does not work that well (anymore).
Jun 16 2023
@Arlolra Thank you for your technical explanation but I have a hard time to use it to answer my questions which are:
- Is the "Story" namespace really only a JSON, so the JsonContentHandler is appropriate?
- If this is JSON, is that really appropriate to have this namespace in https://www.mediawiki.org/wiki/Manual:$wgContentNamespaces?
- Is that normal ("it's a feature, not a bug") that https://id.wikipedia.org/api/rest_v1/page/html/Story%3AWisata_Wajib_di_Toraja returns an error and not the corresponding HTML (like for end-users)?
- If this is normal/wanted that no HTML is returned, then is that appropriate to have a link pointing to https://phabricator.wikimedia.org/T324711 (seems a bit unclear to me).
Jun 10 2023
@cscott @ssastry Really sure this is fixed? Assuming this has been deployed, this is still failing https://id.wikipedia.org/api/rest_v1/page/html/Story%3AWisata_Wajib_di_Toraja. Actually this bug seems to be the reason why we can not generated ZIM offline snapshot of id.wikipedia.org since two quarters. More details about the bug at MWoffliner level at https://github.com/openzim/mwoffliner/issues/1853.
May 20 2023
Apr 18 2023
@Ladsgroup Thank you!
Apr 16 2023
@Dzahn I reopen the task because it seems people can still post and subscribe to the mailing list. This should not be the case (and as moderator I would like to not get notices for this).
Apr 5 2023
Mar 16 2023
@abi_ Thank you for confirming, we will work on this in the next days. Thank you in advance for your patience.
Mar 12 2023
@abi_ Kind of suspect that the strings should be stored in multiple files (like one per language)
Mar 3 2023
Feb 19 2023
@RBrounley_WMF Thank you for opening this ticket, I will follow up.
Feb 7 2023
@abi_ THX!!!
Feb 6 2023
@abi_ I confirm that the github "translatewiki" has write access to the repository and I have just created the qqq.jsonfile, see https://github.com/openzim/mwoffliner/pull/1771.
Feb 1 2023
We are cursed...
Jan 25 2023
Jan 22 2023
Just FYI, no need anymore on MWoffliner side as we use an online object cache meanwhile.
Jan 19 2023
This ticket is really old. We have made many improvement in our toolchain software and infrastructure (many backoff strategies) in the meantime. I can not assess if the problem is still there or if it has been fixed; but whatever the current status, we don't suffer of it anymore. I would be fine to close it.
Jan 16 2023
@abi_ Thank you for the PR, currently under review!
At MWoffliner we have started to study the problem. Because of this ticket but as well because our unstable experience with the usage of this end-point. See https://github.com/openzim/mwoffliner/issues/1730. Hopefuly Wikimedia does provide other better end-points allowing us to retrieve the same information.
Jan 10 2023
@abi_ Thank you! I will create a qqq.json and remove the metadata. When can we expect a first PR from Translatewiki to check the process works fine?
Dec 31 2022
Dec 23 2022
I guess this ticket can be closed?
Dec 12 2022
@Ladsgroup The MWoffliner scraper has already been quite optimised over years. I have no obvious improvement in mind for the moment but we will consider any concrete new proposal.
Would that https://github.com/openzim/mwoffliner/issues/1664 fix the issue, so far we are really not familiar with this new API end-point?
Dec 1 2022
On my end, this looks better now. Thx!
Nov 28 2022
The reported bug seems indeed to have "vanished". Thank you for the good work.
Nov 13 2022
Nov 2 2022
If you can delete the whole thread https://lists.wikimedia.org/hyperkitty/list/wikifr-l@lists.wikimedia.org/thread/J2FU23D4C5ERWIK2LWBYUBTYK3O6KP6Y/, then problem would be solved. It's a pity we can not hide it. I don't like that we manipulate the archive.
Oct 31 2022
Oct 30 2022
@Ladsgroup Thank you but I don't see these two options below the "Add to favorites"... although I'm owner on the list.
Oct 29 2022
@Dzahn Great, thank you very much!
Oct 24 2022
I have achieved to create account an retrieve admin access to the list, but really no clue how to remove the few messages (from the public archive). Not even sure this is possible at all. As a consequence, I have put the whole ml archive in private. Unfortunately, this seems to fail, archive is still accessible at https://lists.wikimedia.org/hyperkitty/list/wikifr-l@lists.wikimedia.org/latest
@nskaggs Not sure this is a question to me, but in the case it needed, could you please change the ZIM mirroring rsync command to:
- request on master.download.kiwix.org in place of download.kiwix.org
- sync the following repositories in addition to wikipedia: wikibooks, wikinews, wikiquote, wikisource, wikiversity, wiktionary, wikivoyage
Oct 16 2022
It seem that this bug partly explains why ZIM files of Wiktionary in English are crappy, see https://github.com/openzim/mwoffliner/pull/1665
Oct 15 2022
It seems the bug reported in T274359 is the same as this one, so reputting here the bug description:
@matmarex Strange to close this ticket considering the bug described in the ticket is not fixed!
Oct 8 2022
During September we have detected that one of the mirror was full and therefore rsync client was keeping download and redownloading things. As a consequence a significant part of the bandwidth and the rsync daemon slots were always busy. We still lack of monitoring solution for this on our side honestly. We should figure a tool and a process to better monitor the server/service. If you have propositions, they are welcome.
@komla What would be the way to proceed:
- Can you delete everything except the DB (no sure what is the same BTW)?
- Should we somehow migrate the DB first?