[Wikitech-l] Re: Recreating CI with Quibble
Thank you both I'll have a look at the updated documentation. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Fri, 19 Apr 2024 at 11:03, Arthur Taylor wrote: > Hi Sebastian, > > I've also been playing around with debugging CI images on my local machine > recently. I've pushed an update to the Quibble docs on Mediawiki [1]. > Hopefully that's helpful - feedback and changes welcome! > > Thanks, > > Arthur > > [1] https://www.mediawiki.org/wiki/Continuous_integration/Quibble > > Am Fr., 19. Apr. 2024 um 10:56 Uhr schrieb Yiannis Giannelos < > jgianne...@wikimedia.org>: > >> Hi, indeed the API request mentioned in the docs doesn't show up the >> quibble images. >> >> The docker registry mentioned in the docs is this one here [1] so you can >> search in this page for the available versions of the quibble images. >> For example this one [2] is built using debian buster and php 8.1. >> >> [1] https://docker-registry.wikimedia.org/ >> [2] >> https://docker-registry.wikimedia.org/releng/quibble-buster-php81/tags/ >> >> On Fri, Apr 19, 2024 at 10:43 AM Sebastian Berlin < >> sebastian.ber...@wikimedia.se> wrote: >> >>> I'm trying to recreate a CI build to debug things locally. I've followed >>> the instructions under >>> https://doc.wikimedia.org/quibble/#reproducing-a-ci-build, but the >>> command for listing Docker images doesn't work. There are no images with >>> "quibble" in the name. Where can I find the available Quibble images? >>> >>> *Sebastian Berlin* >>> Utvecklare/*Developer* >>> Wikimedia Sverige (WMSE) >>> >>> E-post/*E-Mail*: sebastian.ber...@wikimedia.se >>> Telefon/*Phone*: (+46) 0707 - 92 03 84 >>> ___ >>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org >>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org >>> >>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ >> >> ___ >> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org >> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org >> >> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ > > > > -- > Arthur Taylor > Senior Software Engineer > > Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin > Phone: +49 (0)30-577 11 62-0 > https://wikimedia.de > > Keep up to date! Current news and exciting stories about Wikimedia, > Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now > <https://www.wikimedia.de/newsletter/>. > > 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 Charlottenburg, VR 23855 B. > Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, > Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine, > Dr. Christian Humborg > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Recreating CI with Quibble
I'm trying to recreate a CI build to debug things locally. I've followed the instructions under https://doc.wikimedia.org/quibble/#reproducing-a-ci-build, but the command for listing Docker images doesn't work. There are no images with "quibble" in the name. Where can I find the available Quibble images? *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Adding Docker images to the registry via Gitlab
Thank you *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Mon, 11 Mar 2024 at 20:34, Ahmon Dancy wrote: > Sebastian, I created the Speechoid group per your request > https://gitlab.wikimedia.org/groups/repos/mediawiki/services/speechoid > and made you the owner. > > On Thu, Mar 7, 2024 at 4:59 AM Sebastian Berlin < > sebastian.ber...@wikimedia.se> wrote: > >> Thank you to the kind stranger who approved my request on Gitlab >> >> Now I have a followup question: how to add a subgroup under >> repos/mediawiki/services to match what is on Gerrit? It looks like I can't >> create one of those. I found a request form to add subgroup >> <https://phabricator.wikimedia.org/maniphest/task/edit/form/105/>, but >> that one is explicitly for "top-level project group[s] under /repos". >> >> What I'd like to have is a subgroup under repos/mediawiki/services called >> "Speechoid" (changed from "wikispeech" in Gerrit to better describe what >> the service is). >> >> *Sebastian Berlin* >> Utvecklare/*Developer* >> Wikimedia Sverige (WMSE) >> >> E-post/*E-Mail*: sebastian.ber...@wikimedia.se >> Telefon/*Phone*: (+46) 0707 - 92 03 84 >> >> >> On Thu, 7 Mar 2024 at 08:55, Sebastian Berlin < >> sebastian.ber...@wikimedia.se> wrote: >> >>> I'm trying to use the new workflow for uploading Docker images to the >>> registry. Following the link under wikitech:Docker-registry#Downloading >>> images >>> <https://wikitech.wikimedia.org/wiki/Docker-registry#Downloading_images> >>> I ended up on mw:GitLab/Workflows/Deploying services to production >>> <https://www.mediawiki.org/wiki/GitLab/Workflows/Deploying_services_to_production> >>> as the recommended way to do it. >>> >>> As far as I can tell the service repos should live under >>> repos/mediawiki/services/ in Gitlab and you need to have access to the >>> group to import repos there. I clicked on "Request access" in the menu for >>> that group, but I don't think anything has happened since then. Is there >>> anything else I need to do to be granted access? >>> >>> For context, the service I want to add Docker image for is part of >>> Speechoid, a service bundle(?) for Wikispeech >>> <https://www.mediawiki.org/wiki/Extension:Wikispeech>. Currently we >>> have a few other services that have their code on Gerrit >>> <https://gerrit.wikimedia.org/r/admin/repos/q/filter:wikispeech>. >>> >>> *Sebastian Berlin* >>> Utvecklare/*Developer* >>> Wikimedia Sverige (WMSE) >>> >>> E-post/*E-Mail*: sebastian.ber...@wikimedia.se >>> Telefon/*Phone*: (+46) 0707 - 92 03 84 >>> >> ___ >> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org >> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org >> >> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ > > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Adding Docker images to the registry via Gitlab
Thank you to the kind stranger who approved my request on Gitlab Now I have a followup question: how to add a subgroup under repos/mediawiki/services to match what is on Gerrit? It looks like I can't create one of those. I found a request form to add subgroup <https://phabricator.wikimedia.org/maniphest/task/edit/form/105/>, but that one is explicitly for "top-level project group[s] under /repos". What I'd like to have is a subgroup under repos/mediawiki/services called "Speechoid" (changed from "wikispeech" in Gerrit to better describe what the service is). *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Thu, 7 Mar 2024 at 08:55, Sebastian Berlin wrote: > I'm trying to use the new workflow for uploading Docker images to the > registry. Following the link under wikitech:Docker-registry#Downloading > images > <https://wikitech.wikimedia.org/wiki/Docker-registry#Downloading_images> > I ended up on mw:GitLab/Workflows/Deploying services to production > <https://www.mediawiki.org/wiki/GitLab/Workflows/Deploying_services_to_production> > as the recommended way to do it. > > As far as I can tell the service repos should live under > repos/mediawiki/services/ in Gitlab and you need to have access to the > group to import repos there. I clicked on "Request access" in the menu for > that group, but I don't think anything has happened since then. Is there > anything else I need to do to be granted access? > > For context, the service I want to add Docker image for is part of > Speechoid, a service bundle(?) for Wikispeech > <https://www.mediawiki.org/wiki/Extension:Wikispeech>. Currently we have > a few other services that have their code on Gerrit > <https://gerrit.wikimedia.org/r/admin/repos/q/filter:wikispeech>. > > *Sebastian Berlin* > Utvecklare/*Developer* > Wikimedia Sverige (WMSE) > > E-post/*E-Mail*: sebastian.ber...@wikimedia.se > Telefon/*Phone*: (+46) 0707 - 92 03 84 > ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Adding Docker images to the registry via Gitlab
I'm trying to use the new workflow for uploading Docker images to the registry. Following the link under wikitech:Docker-registry#Downloading images <https://wikitech.wikimedia.org/wiki/Docker-registry#Downloading_images> I ended up on mw:GitLab/Workflows/Deploying services to production <https://www.mediawiki.org/wiki/GitLab/Workflows/Deploying_services_to_production> as the recommended way to do it. As far as I can tell the service repos should live under repos/mediawiki/services/ in Gitlab and you need to have access to the group to import repos there. I clicked on "Request access" in the menu for that group, but I don't think anything has happened since then. Is there anything else I need to do to be granted access? For context, the service I want to add Docker image for is part of Speechoid, a service bundle(?) for Wikispeech <https://www.mediawiki.org/wiki/Extension:Wikispeech>. Currently we have a few other services that have their code on Gerrit <https://gerrit.wikimedia.org/r/admin/repos/q/filter:wikispeech>. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Northward Datacentre Switchover (March 2024)
For the time in your timezone: https://zonestamp.toolforge.org/1710943200. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Fri, 23 Feb 2024 at 12:50, effie mouzeli wrote: > Dear all, > > > *"There is nothing permanent except change - Heraclitus"* > On *Wednesday March 20th 2024,* the SRE team will run a planned > datacentre switchover, moving all wikis from *codfw* to *eqiad*. This is > an important periodic test of our tools and procedures, to ensure the wikis > will continue to be available even in the event of major technical issues > in our primary home. It also gives all our SRE and ops teams a chance to do > maintenance and upgrades on systems in codfw that normally run 24 hours a > day. > > The switchover process requires a brief read-only period for all > Foundation-hosted wikis, which will start on *Wednesday March 20th 2024 @ > 14:00 UTC*, and will last for just a few minutes while we execute the > migration as efficiently as possible. All our public and private wikis will > be continuously available for reading, as usual, but editing will be > unavailable during the process. Users will see a notification of the > upcoming maintenance, and anyone still editing will be asked to try again > in a few minutes. > > CommRel will soon begin notifying communities of the read-only window. > > If you like, you can follow along on the day in the public > *#wikimedia-operations* channel on IRC. To report any issues, you can > reach us in *#wikimedia-sre* on IRC, or file a Phabricator ticket > <https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=Datacenter-Switchover>with > the #datacenter-switchover tag; we'll be monitoring closely for reports of > trouble during and after the switchover. The switchover and its preparation > will be tracked under https://phabricator.wikimedia.org/T357547. > > On behalf of the SRE team, please excuse the disruption, and we would like > to thank everyone in various departments who are involved in planning this > work. If you have any questions, please reply directly to this email. > > Kind Regards, > > -effie > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Where to find information about images in the Docker registry
Thank you for the thorough explanation. And thanks to Taavi who just added a python-bookworm image (maybe inspired by my question ). The link to the production images is especially useful when I try to figure out what the different images do. A bit of feedback for the registry that would have helped me and may help in the future: 1. Add links from images to the Docker templates that were used to create them. 2. Mark images that are deprecated so you know to not use them. Take care, *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Fri, 16 Feb 2024 at 11:50, Clément Goubert wrote: > Hi Sebastian, > > We have dropped the "wikimedia-" prefix for base distribution images, you > can safely use the "bookworm" image > <https://docker-registry.wikimedia.org/bookworm> as a base image. > > Regarding python images, the python-build-* images > <https://gerrit.wikimedia.org/r/plugins/gitiles/operations/docker-images/production-images/+/refs/heads/master/images/python-build/> > are for building wheels that can be copied over to a runtime image. The > python3-bullseye > <https://gerrit.wikimedia.org/r/plugins/gitiles/operations/docker-images/production-images/+/refs/heads/master/images/python/bullseye/Dockerfile.template> > and python3-buster > <https://gerrit.wikimedia.org/r/plugins/gitiles/operations/docker-images/production-images/+/refs/heads/master/images/python/buster/Dockerfile.template> > images are runtime images. The python3 image (without suffix) is > deprecated. We do not yet produce a python3-bookworm image, although I > think that can be arranged pretty easily. > > In the meantime, using the bookworm image and using blubber's apt > directive to install python3, python3-pip, and python3-setuptools will give > you the same thing. > > All these images are base and production images > <https://gerrit.wikimedia.org/r/plugins/gitiles/operations/docker-images/production-images/+/refs/heads/master> > images built through docker-pkg <https://doc.wikimedia.org/docker-pkg/> > following the "generations" outlined in our Kubernetes image building > policy > <https://wikitech.wikimedia.org/wiki/Kubernetes/Images#Image_building>. > > Hope this helps, > > On Fri, Feb 16, 2024 at 10:49 AM Sebastian Berlin < > sebastian.ber...@wikimedia.se> wrote: > >> I'm updating some blubberised repos that a colleague of mine created some >> time ago and I'm not sure what base images from the Docker registry >> <https://docker-registry.wikimedia.org/> are the best to use. >> >> For instance, one repo uses >> docker-registry.wikimedia.org/wikimedia-buster as base image in >> .pipeline/blubber.yaml. I thought I'd update to Bookworm as the newest >> stable Debian release, but there is no image "wikimedia-bookworm", only >> "bookworm". I'd like to know what's different in the the ones with the >> wikimedia- prefix. >> >> There are also several different ones for Python, e.g. "python3", >> "python3-buster" and "python3-build-buster". >> >> Is there documentation somewhere or links to repos where I can see what >> Docker or Blubber files were used to create them? >> >> *Sebastian Berlin* >> Utvecklare/*Developer* >> Wikimedia Sverige (WMSE) >> >> E-post/*E-Mail*: sebastian.ber...@wikimedia.se >> Telefon/*Phone*: (+46) 0707 - 92 03 84 >> ___ >> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org >> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org >> >> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ > > > > -- > Clément Goubert (they/them) > Senior SRE > Wikimedia Foundation > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Where to find information about images in the Docker registry
I'm updating some blubberised repos that a colleague of mine created some time ago and I'm not sure what base images from the Docker registry <https://docker-registry.wikimedia.org/> are the best to use. For instance, one repo uses docker-registry.wikimedia.org/wikimedia-buster as base image in .pipeline/blubber.yaml. I thought I'd update to Bookworm as the newest stable Debian release, but there is no image "wikimedia-bookworm", only "bookworm". I'd like to know what's different in the the ones with the wikimedia- prefix. There are also several different ones for Python, e.g. "python3", "python3-buster" and "python3-build-buster". Is there documentation somewhere or links to repos where I can see what Docker or Blubber files were used to create them? *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Python requests broken by urllib3 version 2.x
A word of warning: using `pip freeze` to populate requirements.txt can result in a hard to read (very long) file and other issues: https://medium.com/@tomagee/pip-freeze-requirements-txt-considered-harmful-f0bce66cf895 . *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Fri, 5 May 2023 at 13:17, Amir Sarabadani wrote: > You can also create an empty virtual env, install all requirements and > then do > pip freeze > requirements.txt > > That should take care of pinning > > Am Fr., 5. Mai 2023 um 13:11 Uhr schrieb Lucas Werkmeister < > lucas.werkmeis...@wikimedia.de>: > >> For the general case of Python projects, I’d argue that a better solution >> is to adopt the lockfile pattern (package-lock.json, composer.lock, >> Cargo.lock, etc.) and pin *all* dependencies, and only update them when >> the new versions have been tested and are known to work. pip-tools >> <https://pypi.org/project/pip-tools/> can help with that, for example ( >> requirements.in specifies “loose” dependencies; pip-compile creates a >> pinned requirements.txt; pip-sync installs it; pip-compile -U upgrades >> requirements.txt later; you check both requirements.in and >> requirements.txt into version control.) But I don’t know if that applies >> in your integration/config case. >> >> Am Do., 4. Mai 2023 um 18:08 Uhr schrieb Antoine Musso : >> >>> Hello, >>> >>> This is for python projects. >>> >>> Today, May 4th, urllib3 <https://pypi.org/project/urllib3/#history> has >>> released a new major version 2.0.2 which breaks the extremely popular >>> requests <https://pypi.org/project/requests/> library. >>> >>> The fix is to pin urllib3<2 to prevent the new major version from being >>> installed (example >>> <https://gerrit.wikimedia.org/r/c/integration/config/+/915736/1/tox.ini> >>> ). >>> >>> https://phabricator.wikimedia.org/T335977 >>> >>> Upstream issue: https://github.com/psf/requests/issues/6432 >>> >>> >>> Antoine "hashar" Musso >>> Wikimedia Release Engineering >>> ___ >>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org >>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org >>> >>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ >> >> >> >> -- >> Lucas Werkmeister (he/er) >> Software Engineer >> >> Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin >> Phone: +49 (0)30-577 11 62-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 >> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org >> >> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ > > > > -- > Amir (he/him) > > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Help with sanitized css and templatestyles
As I said above you can't add rules for these classes with TemplateStyles.
All CSS selectors gets `.mw-parser-output` prepended to them. You can see
that in the style element added by TemplateStyles:
>
> .mw-parser-output .mw-parser-output {
> background-color: #E8EFFB;
> border: 5px double #aeb3bc;
> margin-top: 10px;
>
padding: 20px;
> width:98%
> }
>
In this case it will look for a `.mw-parser-output` in another
`.mw-parser-output`, which there are none. There may be some clever CSS
trick to somehow get this to work, but I don't know what that would be.
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.ber...@wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
On Fri, 14 Apr 2023 at 13:54, Martin Domdey wrote:
> Hi Sebastian,
>
> thanks for your reply, but it doesn't work for me.
>
> I tried it with .bodyContent and .mw-parser-output
>
> Please see css:
> https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA/styles.css
> Please see page: https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA (there
> are no styled background color and double borders)
>
> Is there anything that overrides the .bodyContent and .mw-parser-output
> classes?
>
> Kind regards
> Doc Taxon ...
>
>
>
>
> Am Fr., 14. Apr. 2023 um 08:36 Uhr schrieb Sebastian Berlin <
> sebastian.ber...@wikimedia.se>:
>
>> That would be `mw-parser-output` or possibly `mw-parser-output` or
>> `bodyContent` depending on how you define the body. However, the styles
>> added by TemplateStyles are scoped to `mw-parser-output`, as explained in
>> mw.Extension:TemplateStyles#Caveats
>> <https://www.mediawiki.org/wiki/Extension:TemplateStyles#Caveats>. This
>> means you can't add rules to it or anything higher up in the DOM. I don't
>> think you can do what you want (without adding a wrapper) with
>> TemplateStyles.
>>
>> *Sebastian Berlin*
>> Utvecklare/*Developer*
>> Wikimedia Sverige (WMSE)
>>
>> E-post/*E-Mail*: sebastian.ber...@wikimedia.se
>> Telefon/*Phone*: (+46) 0707 - 92 03 84
>>
>>
>> On Fri, 14 Apr 2023 at 01:20, Martin Domdey wrote:
>>
>>> css (commented out):
>>> https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA/styles.css
>>> page: https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA
>>>
>>> Hi, I want to style the page body content with light blue background and
>>> double border like given in linked css (commented out). This style should
>>> be for the whole page body content of
>>> https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA , but I don't
>>> want to use a div container for this.
>>>
>>> What is the id name or class name for the whole page body content to set
>>> the page style like given in linked css?
>>>
>>> Thanks for any help.
>>>
>>> Martin
>>>
>>> ___
>>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
>>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
>>>
>>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>>
>> ___
>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
>>
>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Help with sanitized css and templatestyles
That would be `mw-parser-output` or possibly `mw-parser-output` or `bodyContent` depending on how you define the body. However, the styles added by TemplateStyles are scoped to `mw-parser-output`, as explained in mw.Extension:TemplateStyles#Caveats <https://www.mediawiki.org/wiki/Extension:TemplateStyles#Caveats>. This means you can't add rules to it or anything higher up in the DOM. I don't think you can do what you want (without adding a wrapper) with TemplateStyles. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Fri, 14 Apr 2023 at 01:20, Martin Domdey wrote: > css (commented out): > https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA/styles.css > page: https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA > > Hi, I want to style the page body content with light blue background and > double border like given in linked css (commented out). This style should > be for the whole page body content of > https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/TestA , but I don't want > to use a div container for this. > > What is the id name or class name for the whole page body content to set > the page style like given in linked css? > > Thanks for any help. > > Martin > > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Phabricator downtime (30 minutes) tomorrow between 14:00–16:00 UTC
That's at this time for those of us who are easily confused by time zones: https://zonestamp.toolforge.org/1680012047. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Mon, 27 Mar 2023 at 19:11, Tyler Cipriani wrote: > Hello > > *Phabricator will be down for 30 minutes tomorrow (Tue, 28 Mar 2023) > between 14:00–16:00 UTC* due to network switch upgrades in its data > center row[0]. > > Apologies for the inconvenience :( > > Tyler Cipriani (he/him) > Engineering Manager, Release Engineering > Wikimedia Foundation > > [0]: <https://phabricator.wikimedia.org/T330165> > > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: How to specify version of MW that Jenkins should run?
Thanks for the explanations, Antoine. I'll have a look and see if I can
figure it out. Also agree with what Robert just said that it would be nice
if this was more easily configurable. Not sure what other extensions are
supporting, but I'm guessing not all of them are targeting latest MW alpha.
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.ber...@wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
On Thu, 15 Sept 2022 at 08:56, Robert Vogel via Wikitech-l <
wikitech-l@lists.wikimedia.org> wrote:
> @Hashar: Just wondering, are there any plans to change CI configs after
> moving development/code-review from gerrit to gitlab [1]? Maybe some file
> living in the repo directly rather than using a centralized repo like
> `integration/config`?
>
> [1] https://www.mediawiki.org/wiki/GitLab/Gerrit_to_GitLab
>
> --
> Robert
> --
> *Von:* Antoine Musso
> *Gesendet:* Dienstag, 13. September 2022 15:42
> *An:* Wikitech-l ; Sebastian Berlin <
> sebastian.ber...@wikimedia.se>
> *Betreff:* [Wikitech-l] Re: How to specify version of MW that Jenkins
> should run?
>
> Le 12/09/2022 à 12:20, Sebastian Berlin a écrit :
>
> I'm having some issues with Jenkins running the latest version of MW for
> an extension (Wikispeech
> <https://www.mediawiki.org/wiki/Extension:Wikispeech>). Jenkins run with
> the 1.40 alpha, but we want the extension to support the latest LTS (1.35
> as of right now).
>
> I tried changing in extension.json to:
> "requires": {
> "MediaWiki": "1.35.*"
> }
> which caused an error for Jenkins:
>
> 12:44:09 A dependency error was encountered while installing the extension
> "Wikispeech": Wikispeech is not compatible with the current MediaWiki core
> (version 1.40.0-alpha), it requires: 1.35.*.
>
> The whole log is here: https://phabricator.wikimedia.org/P34482.
>
> How can I specify what version of MW to run with? I've looked at both the
> MW wiki and Wikitech, but hasn't found any instructions for this.
>
> Hello,
>
> There are a lot of good answers and hints in this thread. I will
> complement the answers since I am the one that has introduced the CI system
> currently used for MediaWiki and I used to be in the Wikimedia Foundation
> team which was responsible for MediaWiki development (Platform Engineering,
> disbanded in 2015).
>
> MediaWiki is primarily developed for the Wikimedia project and the focus
> on CI is to ensure that the master branch of MediaWiki core, extensions,
> skins and their composer dependencies are working well together. The CI
> jobs prefixed "wmf-quibble" clone a few dozen of extensions and are
> triggered whenever one send a patch to one of those extensions or
> mediawiki/core. Hence we have more or less a guarantee that the master
> branches of the participating repositories are all working together.
>
> For the deployment to the Wikimedia cluster, we cut a new deployment
> branch (wmf/XXX) directly from the master branch. Since a change could only
> have been merged in the master branch if all the CI jobs passed, we are
> pretty sure that the set of repositories with their wmf branches are
> passing tests. There are some caveats still but that is the rough idea.
>
> The MediaWiki releases are generated from the REL* branches and CI follows
> the same logic. If one send a patch to their extensions REL1_35 branch, CI
> checkout the REL1_35 branch of mediawiki/core and any other repositories
> participating in the job.
>
> Thus if you send a patch to WikiSpeech REL1_35 you would get
> mediawiki/core and Vector at REL1_35 as well ensuring everything works well
> together (and by everything, I mean what ever is covered by tests). But if
> you send a patch for the master branch, it is the master branch of all
> repositories being checked out. In all case the value(s) of the requires
> field in extension.json does not affect the branch used in CI. It is
> entirely based on the convention that all repos are using the same branch.
>
> There are lot of use cases for developers ensuring the master branch is
> compatible with the current development version (master) AND keeping back
> compatibility all the way up to the latest LTS. But that is not enforced by
> CI. I know Translate does it, most probably through manual testing.
>
>
> What we could potentially do is create a job which would inspect the
> extension requires field to get the target branch to test (so if one
> requires 1.35, target the REL1_35 branch) then invoke the testrunner with
> that branch override (--branch REL1_35). Then if you send a patch to
> WikiSpeech master branch, such a job would test its code ag
[Wikitech-l] Re: How to specify version of MW that Jenkins should run?
Thanks for the replies.
The things is that we *want* Jenkins to run with MediaWiki 1.35, which is
why I changed the version in extension.json. There are changes in the
development version that Jenkins runs that aren't compatible with our code.
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.ber...@wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
On Mon, 12 Sept 2022 at 13:04, Derick Alangi wrote:
> Hi,
>
> Based on the error you posted, I could reproduce it locally and I think
> the issue is that I don't think the registration mechanism currently
> supports regular expression for *{ "requires": { "MediaWiki": "..." } },* so,
> it's advised to pick a (minimum) version of MediaWiki core you want your
> extension to work with and then use either of the logical operators: ">=",
> ">", "<=", "<" to cover a range of versions needed.
>
> The most syntax I've seen in almost all extension files is: *{
> "requires": { "MediaWiki": ">= 1.XX.X" } } *for example: *{ "requires": {
> "MediaWiki": ">= 1.35.0" } }.*
>
> Maybe Legoktm has a few more ideas on this and I would also say that
> pinning to a specific version won't work either like "= 1.35.0" or "1.35.0".
>
> Regards!
>
> *--*
>
> *Derick A.*
>
> *From One Developer to Another!*
>
>
> On Mon, Sep 12, 2022 at 11:53 AM Derick Alangi
> wrote:
>
>> Hi Sebastian,
>>
>> Can you change:
>> "requires": {
>> "MediaWiki": "1.35.*"
>> }
>>
>> to:
>> "requires": {
>> "MediaWiki": ">=1.35.0"
>> }
>>
>> Let me know if that helps.
>>
>> *--*
>>
>> *Derick A.*
>>
>> *From One Developer to Another!*
>>
>>
>> On Mon, Sep 12, 2022 at 11:21 AM Sebastian Berlin <
>> sebastian.ber...@wikimedia.se> wrote:
>>
>>> I'm having some issues with Jenkins running the latest version of MW for
>>> an extension (Wikispeech
>>> <https://www.mediawiki.org/wiki/Extension:Wikispeech>). Jenkins run
>>> with the 1.40 alpha, but we want the extension to support the latest LTS
>>> (1.35 as of right now).
>>>
>>> I tried changing in extension.json to:
>>> "requires": {
>>> "MediaWiki": "1.35.*"
>>> }
>>> which caused an error for Jenkins:
>>>
>>>> 12:44:09 A dependency error was encountered while installing the
>>>> extension "Wikispeech": Wikispeech is not compatible with the current
>>>> MediaWiki core (version 1.40.0-alpha), it requires: 1.35.*.
>>>>
>>> The whole log is here: https://phabricator.wikimedia.org/P34482.
>>>
>>> How can I specify what version of MW to run with? I've looked at both
>>> the MW wiki and Wikitech, but hasn't found any instructions for this.
>>>
>>> Best,
>>>
>>> *Sebastian Berlin*
>>> Utvecklare/*Developer*
>>> Wikimedia Sverige (WMSE)
>>>
>>> E-post/*E-Mail*: sebastian.ber...@wikimedia.se
>>> Telefon/*Phone*: (+46) 0707 - 92 03 84
>>> ___
>>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
>>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
>>>
>>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>>
>> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] How to specify version of MW that Jenkins should run?
I'm having some issues with Jenkins running the latest version of MW for an
extension (Wikispeech <https://www.mediawiki.org/wiki/Extension:Wikispeech>).
Jenkins run with the 1.40 alpha, but we want the extension to support the
latest LTS (1.35 as of right now).
I tried changing in extension.json to:
"requires": {
"MediaWiki": "1.35.*"
}
which caused an error for Jenkins:
> 12:44:09 A dependency error was encountered while installing the extension
> "Wikispeech": Wikispeech is not compatible with the current MediaWiki core
> (version 1.40.0-alpha), it requires: 1.35.*.
>
The whole log is here: https://phabricator.wikimedia.org/P34482.
How can I specify what version of MW to run with? I've looked at both the
MW wiki and Wikitech, but hasn't found any instructions for this.
Best,
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.ber...@wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Examples of projects using NLP
There's also Wikispeech <https://meta.wikimedia.org/wiki/Wikispeech> a TTS tool that we (Wikimedia Sverige) are developing. It's currently on the back burner, but hopefully we will have more resources for development soon. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Fri, 24 Jun 2022 at 03:06, Gabriel Altay wrote: > Hello Ilario, > > You might find this blog post I wrote a while back interesting > > https://blog.kensho.com/announcing-the-kensho-derived-wikimedia-dataset-5d1197d72bcf > > In it you can find a brief (and definitely not comprehensive) review of > NLP with Wiki* along with links to an open source Kaggle dataset I built > connecting the plain text of wikipedia, the anchor links between pages, and > the links to wikidata. There are a few notebooks that demonstrate its use > ... my favorite are probably, > > * Pointwise Mutual Information embeddings > https://www.kaggle.com/code/kenshoresearch/kdwd-pmi-word-vectors > * Analyzing the "subclass of" graph from wikidata > https://www.kaggle.com/code/gabrielaltay/kdwd-subclass-path-ner > * Explicit topic modeling > https://www.kaggle.com/code/kenshoresearch/kdwd-explicit-topic-models > > and if you are still looking for more after that, this is the query that > gives more every time you use it :) > > > https://arxiv.org/search/advanced?advanced==AND=wikipedia=abstract=OR=wikidata=abstract_science=y_archives=all_cross_list=include_by=all_dates=_date=_date=_type=submitted_date=show=50=-announced_date_first > > best, > -G > > > > On Thu, Jun 23, 2022 at 4:17 PM Isaac Johnson wrote: > >> Chiming in as a member of the Wikimedia Foundation Research team >> <https://research.wikimedia.org/> (so you'll see that likely biases the >> examples I'm aware of). I'd say that the most common type of NLP that shows >> up in our applications is tokenization / language analysis -- i.e. split >> wikitext into words/sentences. As Trey said, this tokenization is >> non-trivial for English and gets much harder in other languages that >> have more complex constructions / don't use spaces to delimit words >> <https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Spaceless_Writing_Systems_and_Wiki-Projects>. >> These tokens often then become inputs into other types of models that >> aren't necessarily NLP. There are a number of more complex NLP technologies >> too that don't just identify words but try to identify similarities between >> them, translate them, etc. >> >> Some examples below. Additionally, I indicated whether each application >> was rule-based (follow a series of deterministic heuristics) or ML >> (learned, probabilistic model) in case that's of interest: >> >>- Copyedit >> >> <https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task>: >>identifying potential grammar/spelling issues in articles (rule-based). I >>believe there are a number of volunteer-run bots on the wikis as well as >>the under-development tool I linked to, which is a collaboration between >>the Wikimedia Foundation Research team >><https://research.wikimedia.org/> and Growth team >><https://www.mediawiki.org/wiki/Growth> that builds on an open-source >>tool >> >> <https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task/LanguageTool> >>. >>- Link recommendation >> >> <https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Structured_tasks/Add_a_link#Link_recommendation_algorithm>: >>detecting links that could be added to Wikipedia articles. The NLP aspect >>mainly involves accurately parsing wikitext into sentences/words >>(rule-based) and comparing the similarity of the source article and pages >>that are potential target links (ML). Also collaboration between Research >>team and Growth team. >>- Content similarity: various tools such as SuggestBot >><https://en.wikipedia.org/wiki/User:SuggestBot>, RelatedArticles >>Extension <https://www.mediawiki.org/wiki/Extension:RelatedArticles>, >>or GapFinder <https://www.mediawiki.org/wiki/GapFinder> use the morelike >>functionality of CirrusSearch >><https://www.mediawiki.org/wiki/Help:CirrusSearch#Page_weighting> >>backend maintained by the Search team to find Wikipedia articles with >>similar topics -- this is largely finding keyword overlap between content >>with clever pre-processing/weighting as described by Trey. >&g
Re: [Wikitech-l] realtime notifications disabled in Phabricator
> > Also when tasks are moved around on workboards you should see that > again without having to reload the page. > I was very glad to see that this had been fixed when I came back from vacation. Great work! *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Wed, 12 Aug 2020 at 17:30, Tyler Cipriani wrote: > On 20-08-11 15:04:56, Daniel Zahn wrote: > >re: > "aphlict" service had been disabled on Phabricator because it > >caused stability issues. > > > >I am happy to announce that aphlict, the notification service for > >Phabricator using websockets, is now finally back again. > > \o/ This is great news! > > Thank you for working to get this restored. > > Realtime notifications are super useful for us; particularly for train > blocker tasks: very happy this service is back! > > -- Tyler > ___ > 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] realtime notifications disabled in Phabricator
Yes, that was the feature I was referring to. It's very nice to have when planning using workboards, especially when it's done remotely. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Tue, 26 Nov 2019 at 02:11, Daniel Zahn wrote: > Ah. Yes, this sounds like the relatively new feature from: > > https://secure.phabricator.com/T13357 > https://secure.phabricator.com/T4900 > > It is affected then. > > On Mon, Nov 25, 2019 at 6:30 PM David Barratt > wrote: > > > I think they mean that if you have the board open and someone else moves > a > > task, it will update on your end in realtime. > > > > I imagine this *would* be affected by the change. > > > > On Mon, Nov 25, 2019 at 6:28 PM Daniel Zahn wrote: > > > > > On Mon, Nov 25, 2019 at 11:21 AM Sebastian Berlin < > > > sebastian.ber...@wikimedia.se> wrote: > > > > > > > Is that also the reason why tasks don't update in realtime on the > > > > workboards anymore? > > > > > > > > > > If you mean tasks moving from column to column in workboards, no that > is > > > unrelated and done by the > > > Phabricator maintenance bot by Amir Sarabadani, afaik. > > > > > > -- > > > Daniel Zahn > > > Operations Engineer > > > ___ > > > 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 > > > > -- > Daniel Zahn > Operations Engineer > ___ > 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] realtime notifications disabled in Phabricator
Is that also the reason why tasks don't update in realtime on the workboards anymore? I for one thought that was a great addition. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On Tue, 19 Nov 2019 at 22:38, Daniel Zahn wrote: > Phabricator users, > > this is to let you know that the "aphlict" service has been disabled on > Phabricator (for now) because it caused stability issues. > > This means you will not get realtime (pop-up) notifications on Phabricator. > (If you had those enabled in the first place). > > Regular notifications (that do not pop-up) and emails are not affected by > this. > > https://phabricator.wikimedia.org/T238593 > > -- > Daniel Zahn > Operations Engineer > ___ > 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] PHPUnit error: Cannot access the database: Unknown database
That did it. Thanks a lot. I added a line about this to the Wiki-page. Best, *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On 25 October 2017 at 12:39, Brian Wolff <bawo...@gmail.com> wrote: > Try passing > > --wiki wiki > > As a command line argument to the script. (Assuming wiki is the db name. > Otherwise pass --wiki dbname_here ) > > -- > bawolff > > On Wednesday, October 25, 2017, Sebastian Berlin < > sebastian.ber...@wikimedia.se> wrote: > > I'm having trouble running PHPUnit for the extension I'm developing > > (Wikispeech), in Vagrant. I followed the instructions on > > > https://www.mediawiki.org/wiki/Manual:PHP_unit_testing/ > Writing_unit_tests_for_extensions#Run_your_tests > , > > i.e. `tests/phpunit/phpunit.php extensions/Wikispeech/tests`, and got the > > error: > > > >> Fatal error: Uncaught exception 'Wikimedia\Rdbms\DBConnectionError' > with > >> message 'Cannot access the database: Unknown database > >> 'extensions/Wikispeech/tests/phpunit/ApiWikispeechTest.php' > (127.0.0.1)' > in > >> /vagrant/mediawiki/includes/libs/rdbms/database/Database.php:800 > >> > > For full log, see https://phabricator.wikimedia.org/P6176. > > > > Does anyone know what's causing this? > > > > Previously I've run the tests with `phpunit extensions/Wikispeech/tests` > > which I realize isn't the correct way, after reading the Wiki-page again. > > However, this didn't work after I reinstalled Vagrant (due to various > other > > problems). > > > > All the best, > > > > *Sebastian Berlin* > > Utvecklare/*Developer* > > Wikimedia Sverige (WMSE) > > > > E-post/*E-Mail*: sebastian.ber...@wikimedia.se > > Telefon/*Phone*: (+46) 0707 - 92 03 84 > > ___ > > 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
[Wikitech-l] PHPUnit error: Cannot access the database: Unknown database
I'm having trouble running PHPUnit for the extension I'm developing (Wikispeech), in Vagrant. I followed the instructions on https://www.mediawiki.org/wiki/Manual:PHP_unit_testing/Writing_unit_tests_for_extensions#Run_your_tests, i.e. `tests/phpunit/phpunit.php extensions/Wikispeech/tests`, and got the error: > Fatal error: Uncaught exception 'Wikimedia\Rdbms\DBConnectionError' with > message 'Cannot access the database: Unknown database > 'extensions/Wikispeech/tests/phpunit/ApiWikispeechTest.php' (127.0.0.1)' in > /vagrant/mediawiki/includes/libs/rdbms/database/Database.php:800 > For full log, see https://phabricator.wikimedia.org/P6176. Does anyone know what's causing this? Previously I've run the tests with `phpunit extensions/Wikispeech/tests` which I realize isn't the correct way, after reading the Wiki-page again. However, this didn't work after I reinstalled Vagrant (due to various other problems). All the best, *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.ber...@wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
