Wikitech-l March 2012

wikitech-l@lists.wikimedia.org

155 participants
204 discussions

Re: [Wikitech-l] Dropping support for the automatic /index.php/Article
by bawolff 25 Mar '12

25 Mar '12

>For awhile we've supported automatic detection guessing if the webserver >supports PATH_INFO and if so automatically using /index.php/$1 for the >article path. I believe this even predates our better REQUEST_URI handling. > >I'm considering the idea of dropping support for this automatic setup. [..] I don't really like the idea of dropping it, unless our detection of it not working really does suck. Moving servers is going to break things no matter what. This is especially true now that $wgServer is set explicitly instead of auto-detected. If we're worried about auto-detection failing, we could do better auto-detection in the install script ( Make an ajax request to some script /mw-config/path_info.php/test and see if it can properly extract the path info). -bawolff

1 0

English Wikipedia slow to load
by MZMcBride 25 Mar '12

25 Mar '12

Hi. There are over a dozen reports of general slowness with the English Wikipedia: https://en.wikipedia.org/w/index.php?oldid=483631204#is_it_me_or_is_wiki_ver y_slow.3F As I browsed and edited the site today, I experienced similar issues (painful slowness on intermittent page loads, loading half a page and then stalling, etc.). Is anyone from ops or engineering looking into this? I've filed a bug about this as well: <https://bugzilla.wikimedia.org/show_bug.cgi?id=35448>. It may be that this is a known issue (due to schema changes or whatever else), but I don't think anyone from ops or engineering has commented on the village pump (or elsewhere?). Can someone please take a look at what's going on? MZMcBride

6 9

migrating a non-WMF extension to Git
by Amir E. Aharoni 25 Mar '12

25 Mar '12

Hi, I posted a question at https://www.mediawiki.org/wiki/Talk:Git/New_repositories , but i'm not sure that that page is watched, so i'm poking here, too: I couldn't find any guide for migrating an existing extension from SVN to Git. The extension in question is TranslationNotifications, which is not currently WMF-deployed, but probably will be soon. And the question is relevant for all other extension. Thank you. -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

4 11

https://www.mediawiki.org/wiki/Download_from_Git
by Thomas Gries 24 Mar '12

24 Mar '12

https://www.mediawiki.org/wiki/Download_from_Git This page should be extended - with a short section of an example /how to download extensions /like TitleKey (anonymous / as developer) ( Extension:TitleKey is the example which is used on corresponding page https://www.mediawiki.org/wiki/Subversion#Check_out ). - with a link where we can see the source/before downloading/

2 1

Manual:Subversion - pls add the corresponding git commands to each example
by Thomas Gries 24 Mar '12

24 Mar '12

I would appreciate if someone please adds - for each example - the corresponding (anonymous https://) git commands to the "checkout" examples on https://www.mediawiki.org/wiki/Subversion#Check_out ? Purpose: to update the documentation for downloaders how to fetch the recent versions of MediaWiki and its extensions from git. This is also listed as a "To-Do" in https://www.mediawiki.org/wiki/Git/Conversion#March_2012 "change links on mediawiki.org ".

1 0

Extensions which were migrated to git
by Thomas Gries 24 Mar '12

24 Mar '12

Can someone please adjust the Template for Extensions https://www.mediawiki.org/wiki/Template:Extension so that an additional (new) git download and browse source parameter becomes available? I need this (for example) for https://www.mediawiki.org/wiki/RSS .

2 1

upgrade to 1.18.2 with git
by john＠phillyrd.org 24 Mar '12

24 Mar '12

I followed the instruction in the announcement email: "To do a simple Git clone, the command is: git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git" however this gives me version 1.20alpha. 'git branch' shows no branches other than master. I can't find any documentation at mediawiki.org do I need to clone a different repository? ~~John Laurino

5 5

Jenkins and MediaWiki
by Antoine Musso 23 Mar '12

23 Mar '12

Hello! Jenkins is somehow back in action. I have disabled IRC notification to avoid any possible spam over the week-end. Jenkins is connected directly to Gerrit and get notified whenever a change is submitted in any repository. Whenever a change is made to mediawiki/core.git, Jenkins trigger the MediaWiki-GIT-Fetching job which will get fetch the change. Then, two other jobs are triggered on that code: - MediaWiki-Tests-Databaseless -> runs tests using make databaseless and an empty LocalSettings.php - MediaWiki-Tests-Parser -> runs the parser tests using a sqlite backend Over the course of next week, I will create the remaining jobs. You can have a look at the current status at: https://integration.mediawiki.org/ci/job/MediaWiki-GIT-Fetching/ For each build, it list the gerrit change number and patchset. That will give a good overview of what is going wrong. Known bug: - somehow, tests results from child jobs are not aggregated back up to the main MediaWiki-GIT-Fetching job. - there might be some race conditions when several changes are submitted at the same time. -- Antoine "hashar" Musso

1 0

API problem
by Bináris 23 Mar '12

23 Mar '12

Hi, I was playing with properties as written at https://www.mediawiki.org/wiki/API:Properties#Info:_Parameters I spent a lot of time, but I cannot get the properties watched and preload anyway. Preload is empty for an existing page and None for a non-existing page with preload; watched doeas not appear at all. I tried it in browser as well as with bot, logged in as admin. Could somebody please provide me a working link that shows watched and preload? Page example with preload<http://hu.wikipedia.org/w/index.php?action=edit&preload=Wikip%C3%A9dia%3AJa…> I am interested in new pages in namespace MediaWiki where a text is preloaded but without a preload subpage (I guess taken from translatewiki). Do they qualify as preload and may be got by API? -- Bináris

2 5

Git migration: documentation and short-term considerations
by Rob Lanphier 23 Mar '12

23 Mar '12

Hi everyone, Git day is upon us (actual cutover happened a few hours ago). Chad, Antoine, Roan, Sumana and many others made a heroic effort to get this pushed out while many of us were instead doing budget stuff (Sumana gets bonus points for doing both budget stuff and Git stuff). My role in this process: copy and paste this email out of Etherpad ;-) Important documentation: * https://www.mediawiki.org/wiki/Git <- The hub * Requesting an account (Git and Labs share account infrastructure): https://www.mediawiki.org/wiki/Project:Labsconsole_accounts * The list of repositories: https://gerrit.wikimedia.org/r/#admin,projects * The list of extensions that have moved: https://gerrit.wikimedia.org/mediawiki-extensions.txt * How we're dealing with Gerrit project ownership: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/59681 (give us a day to set up the page/templates for requesting Gerrit project ownership) Since a lot of people are likely curious, now is a good time to talk about what our deployment strategy is going to be in the short term, and how this migration affects our plans moving forward. In the short term, we're still deploying from 1.19wmf1 in SVN. Therefore, things that need immediate deployment will need to be manually merged back to the deployment branch (and all non-urgent deployments should hang on until we finish the work here). We plan to be a little more relaxed for this short period about things going directly into 1.19wmf1. Deployment from fenari doesn't change yet. We're currently planning security releases for 1.17, 1.18, and 1.19. These will be released from git. In the medium term, we plan to have far more frequent deployments, starting as early as April 9. More in a separate email on the subject. Moving over the deployment process and ironing out the remaining issues with our current migrated projects is Chad and Antoine's number one priority right now, so there should be significant continuing progress on this over the next several days. General workflow issues are Chad's responsibility. The work to support Translatewiki is well underway, and Antoine is taking the lead with that. Thanks for your patience with this move. We hope you enjoy working with Git (or, if you're currently a skeptic, at least come to appreciate it). With the combination of Git and the workflow changes it enables, we're pretty excited by our new ability to deploy code more frequently, and we're pretty optimistic that we'll be able to actually get that benefit sooner rather than later. Rob (and Chad, and Sumana)

9 13

← Newer
1
...
5
6
7
8
9
10
11
...
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l March 2012