Thanks Nicholas for the response, apologies this isn't threaded, I was
subscribed only to a daily digest.
Here's a version of the notebook that (sometimes) shows the lost connection
problem.
https://public.paws.wmcloud.org/User:Mat_kelcey/timeout%20and%20OOM%20repro…
It either fails directly with OOM or we lose connection to the server; I
think it's as simple as it being just a long running query with a large
result set. I'm thinking perhaps PAWS just isn't right for these types of
queries? Not sure what tuning I can do, re: PAWS config or the query
itself, I think I just need to learn more about other execution
environments.
In any case I have a way of running the query with minimal postprocessing
that doesn't OOM, that I can write to disk and download to my local machine
to play with. That's fine for now as I poke around with the dataset.
Cheers,
Mat
> hi all!
>
> as part of task "Look into matching images of the same painting"
> https://phabricator.wikimedia.org/T131553
> <https://phabricator.wikimedia.org/T131553>
> i've been trying to reproduce some sql queries as described in
>
https://github.com/multichill/toollabs/blob/master/bot/wikidata/find_painti…
>
> where as usually these scripts would be running under toolforge (or some
> other bot execution environment i'm not sure of) i've been finding these
> long running queries timeout under PAWS
>
> does anyone have suggestions / examples for running queries such as
>
http://tools.wmflabs.org/multichill/queries2/commons/paintings_without_wiki…
> under PAWS?
>
> cheers,
> mat
> ____
Dear Wikimedians,
Few months before we released the Spell4Wiki app. On that time Tamil
language only available for Spell4Wiktionary option. After that some of
wikimedians are requested to add their language. As of now 5 languages are
added in Spell4Wiktionary options and one more new language added.
*Short description about Spell4Wiki*
Spell4Wiki a GPLv3 licensed app to record and upload audio for
Wiktionary words to Wikimedia Commons. The app is also a multilingual
dictionary based on Wiktionary.
*App link : *
https://play.google.com/store/apps/details?id=com.manimarank.spell4wiki
*Update details*
- German, Bengali, Russian & Swedish languages are added in
Spell4Wiktionary option. Now, they can contribute their wiktionary words
easily.
- Dagbani language newly added. Actually the Dagbani languge don't have
Wiktionary. But, they can upload audios by using Spell4WordList and
Spell4Word options.
- Major Crashes and some defects are fixed
- New entry added in Tamil Embassy https://ta.wiktionary.org/s/4ojr
Dagbani language Wikimedians are most actively using this app and as of now
contributed voice for 1800+ words. Actually they plan to upload 4000 words
within this year's end.
I would like to thank the following people, for helping to add new language
and reporting issues.
Thanks to ZI_Jony, Info-former, Jan Ainali, Ganesh, Masssly,
andrew.krizhanovsky & Infovarius
*Install and try the app :*
https://play.google.com/store/apps/details?id=com.manimarank.spell4wiki
*Do you want to add your language ?*
Fill this form : https://forms.gle/NWEts2dYoGiGmQbu6
Check here :
https://github.com/manimaran96/Spell4Wiki/blob/master/docs/CONTRIBUTING.md
*More details :*
- https://commons.wikimedia.org/wiki/Commons:Spell4Wiki
- https://manimaran96.wordpress.com/category/android-apps/spell4wiki/
--
Manimaran K
https://manimaran96.wordpress.com
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. If there are additional topics for TechCom to review, please let
us know by replying to this email. However, please keep discussion about
individual RFCs to the Phabricator tickets.
Activity since Tuesday 2020-12-08 on the following boards:
https://phabricator.wikimedia.org/tag/techcom/https://phabricator.wikimedia.org/tag/techcom-rfc/
Committee inbox: (none)
Committee board activity:
- T42787 <https://phabricator.wikimedia.org/T42787> Remove legacy ajax
interface
- I moved from Inbox to Watching
- T267213 <https://phabricator.wikimedia.org/T267213> Create WikiTeq
group on Gerrit
- Kizule is asking for an update.
- It seems there are two things to do: create the group and update
the policy.
New RFCs: (none)
Phase progression: (none)
IRC meeting request: (none)
Other RFC activity:
- T263841 <https://phabricator.wikimedia.org/T263841> RFC: Expand API
title generator to support other generated data
- There is a new proposal text. Please comment.
- T259771 <https://phabricator.wikimedia.org/T259771>: RFC: Drop support
for database upgrade older than two LTS releases.
- Discussion on the task. To me it looks mostly in favor or commenting
that some of the problems are not fully solved by this proposal.
- T268326 <https://phabricator.wikimedia.org/T268326> RFC: Amendment to
the Stable interface policy (November 2020)
- Feedback given about the proposed 3 month minimum period
- T119173 <https://phabricator.wikimedia.org/T119173>: RFC: Discourage
use of MySQL's ENUM type.
- Amir showed how to automatically generate on-wiki documentation for
tables.
- T133452 <https://phabricator.wikimedia.org/T133452>: RFC: Create
temporary accounts for anonymous editors.
- Many comments after Tim proposed to use cloaks (see his comment in the
task for details)
- T214362 <https://phabricator.wikimedia.org/T214362>: RFC: Store
WikibaseQualityConstraint check data in persistent storage.
- Krinkle asked for clarifications. Lucas responded with a comment and
Lydia offered to have it explained in a call.
- T208776 <https://phabricator.wikimedia.org/T208776>: RFC: Introduce
PageIdentity to be used instead of WikiPage.
- Krinkle and Daniel discuss implementation details in context of what's
best for type safety, clarity and migration.
-Niklas
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. If there are additional topics for TechCom to review, please let us
know by replying to this email. However, please keep discussion about individual
RFCs to the Phabricator tickets.
Activity since Monday YYYY-MM-DD on the following boards:
https://phabricator.wikimedia.org/tag/techcom/https://phabricator.wikimedia.org/tag/techcom-rfc/
Committee inbox:
* Remove legacy ajax interface T42787
<https://phabricator.wikimedia.org/T42787>
o Very old task. We should just do it.
Committee board activity:
* Create WikiTeq group on Gerrit T267213
<https://phabricator.wikimedia.org/T267213>
o We should just add WikiTeq to the policy page
New RFCs: none
Phase progression:
* PHP microservice for containerized shell execution (aka ShellBox) T260330
<https://phabricator.wikimedia.org/T260330>
o Last call should have ended last week. Some discussion during last call
period. New comment asking why this should be written in PHP.
o Code is already merged, though not used yet.
o Can probably be approved.
* Amendment to the Stable interface policy T268326
<https://phabricator.wikimedia.org/T268326>
o Question about new requirement to wait at least thee month between hard
deprecation and removal.
o Moved to phase 4
* PageIdentity T208776 <https://phabricator.wikimedia.org/T208776>
o Thiemo (WMDE) asking about some details
o Daniel would like this to go on last call.
Other RFC activity:
* Expand API title generator to support other generated data T263841
<https://phabricator.wikimedia.org/T263841>
o Tim says this is fine and should go ahead
o Do we need a last call?
* Provide mechanism for defining and utilizing configuration sets for local
development and browser / API-testing tests T267928
<https://phabricator.wikimedia.org/T267928>
o Continued discussion after IRC meeting
o Adam Wight emphasizes the need to have config controlled per-request,
rather than changing config on disk.
* Store WikibaseQualityConstraint check data in persistent storage T214362
<https://phabricator.wikimedia.org/T214362>
o WMDE would like this to move forward. Resourcing is not really clear.
--
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation
Hi all,
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
- 1.31.11
- 1.35.1
This will resolve 5 issues in MediaWiki core (1 of which isn't applicable
to MediaWiki 1.31 at all), and also includes some fixes previously
committed to git, including minor security and hardening patches along with
bug fixes included for maintenance reasons.
We will make the fixes available in these respective release branches, and
also master. Tarballs will be available for the above mentioned point
releases as well.
A summary of some of the security fixes that have gone into non-bundled
MediaWiki extensions will also follow.
As per the MediaWiki Version lifecycle [1], November 2020 was the scheduled
EOL date for the REL1_34. MediaWiki 1.35.1 will be supported until at least
September 2023, and would be the recommended upgrade path for anyone still
using 1.34.
[1] https://www.mediawiki.org/wiki/Version_lifecycle