[Wikitech-l] The difference between fileexists-no-change and backend-fail-alreadyexists for action=upload

[Chen Xinyan]

Hi there,

Hope I've found the correct list for asking this question.

I was setting up a CI test case for my MediaWiki Client Library to run a bot 
that will upload a file to https://en.wikipedia.beta.wmflabs.org in chunked 
stash mode. For most of the time, when I perform the final upload with filekey 
parameter, I will receive a fileexists-no-change error from the MW API server. 
This is expected, as there is already a same file with the same title on the 
site. However, today I received backend-fail-alreadyexists. The error message 
looks like

backend-fail-alreadyexists: The file 
"mwstore://local-swift-eqiad/local-public/archive/9/95/20191116051316!Test_image.jpg"
 already exists.

Does this error usually occurs when user tries to upload the same file? What's 
the difference between fileexists-no-change and backend-fail-alreadyexists?

Thanks,
Xinyan

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Max Semenik]

On Fri, Nov 15, 2019 at 7:19 PM Sam Wilson  wrote:

> Where does the mediawiki/mediawiki package come from? It's no longer on
> Packagist; how does Composer know where to get it? It should certainly
> not appear as a requirement for any package.
>

ComposerHookHandler adds it programmatically.

As for removing the functionality: do you mean the functionality of the
> Composer merge plugin? i.e. that we can load dependencies in the
> MediaWiki root directory, rather than within each extension's directory?
>

I mean ComposerHookHandler and friends.


-- 
Best regards,
Max Semenik ([[User:MaxSem]])
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Sam Wilson]

Where does the mediawiki/mediawiki package come from? It's no longer on 
Packagist; how does Composer know where to get it? It should certainly 
not appear as a requirement for any package.


As for removing the functionality: do you mean the functionality of the 
Composer merge plugin? i.e. that we can load dependencies in the 
MediaWiki root directory, rather than within each extension's directory?


On 15/11/19 7:16 pm, Max Semenik wrote:

On Fri, Nov 15, 2019 at 8:16 AM Brad Jorsch (Anomie) 
wrote:


It also predated T467 RfC: Extension management with Composer
, which rejected the proposal to
manage extensions via composer.


Which raises the question: should this functionality stay in MediaWiki at
all?



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Max Semenik]

On Fri, Nov 15, 2019 at 8:16 AM Brad Jorsch (Anomie) 
wrote:

> It also predated T467 RfC: Extension management with Composer
> , which rejected the proposal to
> manage extensions via composer.


Which raises the question: should this functionality stay in MediaWiki at
all?

-- 
Best regards,
Max Semenik ([[User:MaxSem]])
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] WM Technical Conference 2019 update - day 4

[Deb Tankersley]

Hello and thanks for reading!

We wanted to give a quick update on what happened during the final day of
the Wikimedia Technical Conference
, in
Atlanta, Georgia.

*Friday
,
November 15, 2019:*
The first morning session looked at LocalDev: complex multi-service
MediaWiki development and use cases / personas that need tailored
development environments (ticket ).
We also discussed API Integration Testing concentrating on functions,
stories, and scenarios (ticket ).

After we dot voted on Thursday morning, we finished up the last
unconference sessions on Friday:

   - New CI / Argo k8s for CI workloads challenges, details, paths forward (
   ticket )
   - Wikimedia Space solves all your (communication) problems* (ticket
   )
   - The test pyramid and speeding up your results (ticket
   )
   - kiwix / open ZIM. portfolio software stack, future ?, tech needs
   - What is a technical contribution? (ticket
   )
   - JS Framework Experience Sharing (ticket
   )
   - Global templates! Let's flesh it out (ticket
   )
   - Logspam - how do we have less / surface it to the right people? (ticket
   )
   - PHPUnit: what can we improve, can we remove phpunit.php wrapper
   script, etc (ticket )
   - What user analytics would help you as a developer? (ticket
   )
   - I'll help you replace Travis with Actions for GitHub-mastered repos (
   ticket )
   - The gradation of participation - what is a third party? Defining a
   common phrase with a common – and shared – understanding (ticket
   )
   - Ukulele to wikitext (ticket 
   )

The last session was a Recap and Reflection gathering using a world cafe
style discussion (ticket ) -
each of the 5 themes have a notes document that is in their respective epic
tickets:

   - Local Development and onboarding (ticket
   )
   - Testing (ticket )
   - Deploying and Hosting (ticket
   )
   - Standardization Decisions (ticket
   )
   - People and Processes (ticket
   )

We also did a group photo

in-between raindrops!

We ended the day with our last documentation sprint, copying info from the
day's sessions and moving them into the phabricator tickets (to keep all
the data in one place), taking pictures of the session sticky notes /
diagrams, and then adding them also into the phabricator tickets. whew!

Photos and documentation that have been uploaded can be viewed using this
category

(look
for day 4
)
on Commons: Category:Wikimedia Technical Conference 2019

(sample
demo: ukulele to wikitext

video).


Cheers,

The Wikimedia Technical Conference Program Committee


--

deb tankersley (she/her)

program manager, engineering

Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] help once

[Zoran Dori]

Hi,
I didn't quite understand this mail. Can you clarify?

Best regards,
Zoran.

pet, 15. nov 2019. 20:16 Fokou Joel  je napisao/la:

> I am a student in the Faculty of Engineering and Technology in
> University of Buea(Cameroon).
> Thank you!
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] help once

[Fokou Joel]

I am a student in the Faculty of Engineering and Technology in
University of Buea(Cameroon).
Thank you!

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Brad Jorsch (Anomie)]

On Fri, Nov 15, 2019 at 11:06 AM Lucas Werkmeister <
lucas.werkmeis...@wikimedia.de> wrote:

> That was six years ago, predating extension registration – I would assume
> that nowadays extensions are supposed to declare their compatible MediaWiki
> versions in extension.json
> <
> https://www.mediawiki.org/wiki/Manual:Extension_registration#Requirements_(dependencies)
> >
> (details
> ).
>

It also predated T467 RfC: Extension management with Composer
, which rejected the proposal to
manage extensions via composer.

I think you assume correctly.

-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Lucas Werkmeister]

That was six years ago, predating extension registration – I would assume
that nowadays extensions are supposed to declare their compatible MediaWiki
versions in extension.json

(details
).

Cheers,
Lucas

Am Fr., 15. Nov. 2019 um 16:38 Uhr schrieb Stephan Gambke via Wikitech-l <
wikitech-l@lists.wikimedia.org>:

> See
> https://github.com/wikimedia/mediawiki/commit/3307d4957925df319df2b84cfc3e6f1680d0632a
>
> "This change allows extensions to specify they depend on a specific
> version or version range of MediaWiki. This is done by adding the package
> mediawiki/mediawiki in their composer.json require section."
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, November 15, 2019 4:15 PM, David Barratt <
> dbarr...@wikimedia.org> wrote:
>
> > as far as I know, extensions shouldn't be declaring a dependency on
> MediaWiki in composer.json and if one is, it should probably be fixed.
> >
> > On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l <
> wikitech-l@lists.wikimedia.org> wrote:
> >
> >> When running `composer update` MediaWiki injects a mediawiki/mediawiki
> package, so extensions can declare a dependency on a particular MW version
> range.
> >> However, when doing a `composer update --dry-run` this package gets not
> injected causing the dry run to fail.
> >>
> >> Does anybody know a solution/workaround?
> >>
> >> Stephan
> >>
> >> ___
> >> Wikitech-l mailing list
> >> Wikitech-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Lucas Werkmeister (he/er)
Full Stack Developer

Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de

Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us to achieve our vision!
https://spenden.wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Stephan Gambke via Wikitech-l]

See 
https://github.com/wikimedia/mediawiki/commit/3307d4957925df319df2b84cfc3e6f1680d0632a

"This change allows extensions to specify they depend on a specific version or 
version range of MediaWiki. This is done by adding the package 
mediawiki/mediawiki in their composer.json require section."

‐‐‐ Original Message ‐‐‐
On Friday, November 15, 2019 4:15 PM, David Barratt  
wrote:

> as far as I know, extensions shouldn't be declaring a dependency on MediaWiki 
> in composer.json and if one is, it should probably be fixed.
>
> On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l 
>  wrote:
>
>> When running `composer update` MediaWiki injects a mediawiki/mediawiki 
>> package, so extensions can declare a dependency on a particular MW version 
>> range.
>> However, when doing a `composer update --dry-run` this package gets not 
>> injected causing the dry run to fail.
>>
>> Does anybody know a solution/workaround?
>>
>> Stephan
>>
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Stephan Gambke via Wikitech-l]

To enable extensions to declare a version constraint on MW, so an incompatible 
version of an extension is not installed in the first place instead of crashing 
MW later on.

Stephan

‐‐‐ Original Message ‐‐‐
On Friday, November 15, 2019 4:27 PM, Florian Schmidt 
 wrote:

> Extensions can express a dependency to mediawiki core in their 
> extension.json. not sure where, how and why a non-existing composer package 
> should be injected to a composer run.
>
> Am 15.11.2019 10:15 schrieb David Barratt :
>
>> as far as I know, extensions shouldn't be declaring a dependency on
>> MediaWiki in composer.json and if one is, it should probably be fixed.
>>
>> On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l <
>> wikitech-l@lists.wikimedia.org> wrote:
>>
>>>
>>> When running `composer update` MediaWiki injects a mediawiki/mediawiki
>>> package, so extensions can declare a dependency on a particular MW version
>>> range.
>>> However, when doing a `composer update --dry-run` this package gets not
>>> injected causing the dry run to fail.
>>>
>>> Does anybody know a solution/workaround?
>>>
>>> Stephan
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> Wikitech-l mailing list
>>> Wikitech-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[David Barratt]

as far as I know, extensions shouldn't be declaring a dependency on
MediaWiki in composer.json and if one is, it should probably be fixed.

On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l <
wikitech-l@lists.wikimedia.org> wrote:

>
> When running `composer update` MediaWiki injects a mediawiki/mediawiki
> package, so extensions can declare a dependency on a particular MW version
> range.
> However, when doing a `composer update --dry-run` this package gets not
> injected causing the dry run to fail.
>
> Does anybody know a solution/workaround?
>
> Stephan
>
>
>
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

[Stephan Gambke via Wikitech-l]

When running `composer update` MediaWiki injects a mediawiki/mediawiki package, 
so extensions can declare a dependency on a particular MW version range.
However, when doing a `composer update --dry-run` this package gets not 
injected causing the dry run to fail.

Does anybody know a solution/workaround?

Stephan





___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l