MediaWiki  1.23.2
Utf8Test.php File Reference

Runs the UTF-8 decoder test at: More...

Go to the source code of this file.


 testLine ( $test, $line, &$total, &$success, &$failed, $columns, $exceptions, $verbose)


if(! $in$columns = 0
 $failed = 0
while(false !==( $line=fgets( $in))) if(! $columns) $ignore
 $in = fopen( "UTF-8-test.txt", "rt" )
 $section = null
 $sectionTests = array( '3.4' )
 $success = 0
 $test = ''
 $total = 0
 $verbose = false
 if (PHP_SAPI !='cli')

Detailed Description

Runs the UTF-8 decoder test at:

Copyright © 2004 Brion Vibber

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

Definition in file Utf8Test.php.

Function Documentation

◆ testLine()

testLine (   $test,

Definition at line 127 of file Utf8Test.php.

References $columns, $exceptions, $failed, $line, $ok, $success, $test, $total, and $verbose.

Variable Documentation

◆ $columns

◆ $exceptions

Initial value:
# Tests that should mark invalid characters due to using long
# sequences beyond what is now considered legal.
'2.1.5', '2.1.6', '2.2.4', '2.2.5', '2.2.6', '2.3.5',
# Literal 0xffff, which is illegal
'2.2.3' )

Definition at line 72 of file Utf8Test.php.

Referenced by ResourceLoader\makeModuleResponse(), ApiMain\matchOrigin(), and testLine().

◆ $failed

◆ $ignore

while (false !==($line=fgets($in))) if (! $columns) $ignore
Initial value:
# These two lines actually seem to be corrupt
'2.1.1', '2.2.1' )

Definition at line 68 of file Utf8Test.php.

Referenced by FindHooks\printArray(), DatabaseOracle\reportQueryError(), and DatabaseBase\reportQueryError().

◆ $in

◆ $longTests

Initial value:
# These tests span multiple lines
'3.1.9', '3.2.1', '3.2.2', '3.2.3', '3.2.4', '3.2.5',
'3.4' )

Definition at line 80 of file Utf8Test.php.

◆ $section

$section = null

Definition at line 88 of file Utf8Test.php.

Referenced by JobQueueFederated\__construct(), LBFactoryMulti\__construct(), HTMLForm\__construct(), PoolCounterRedis\acquireForAnyone(), PoolCounterRedis\acquireForMe(), RedisBagOStuff\add(), HTMLForm\addFooterText(), CategoryViewer\addFragmentToTitle(), HTMLForm\addHeaderText(), ParserOutput\addHeadItem(), SwiftFileBackend\addMissingMetadata(), FileOpBatch\attempt(), SkinTemplate\buildContentNavigationUrls(), RedisBagOStuff\cas(), FileBackendStore\concatenate(), FileBackendStore\copyInternal(), FileBackendStore\createInternal(), RedisBagOStuff\delete(), FileBackendStore\deleteInternal(), FileBackendStore\describeInternal(), HTMLForm\displaySection(), FileBackendStore\doClean(), Skin\doEditSectionLink(), FileBackendStore\doOperationsInternal(), FileBackendStore\doPrepare(), FileBackendStore\doPublish(), FileBackendStore\doQuickOperationsInternal(), FileBackendStore\doSecure(), ApiEditPage\execute(), VectorTemplate\execute(), FileBackendStore\executeOpHandlesInternal(), FileBackendStore\fileExists(), Linker\formatAutocommentsCallback(), Linker\formatTemplates(), Linker\generateTOC(), RedisBagOStuff\get(), MessageCache\get(), SwiftFileBackend\getContainerStat(), SwiftFileBackend\getDirListPageInternal(), FileBackendStore\getFileContentsMulti(), SwiftFileBackend\getFileListPageInternal(), FileBackendStore\getFileProps(), FileBackendStore\getFileSha1Base36(), FileBackendStore\getFileSize(), FileBackendStore\getFileStat(), FileBackendStore\getFileTimestamp(), FileBackendStore\getFileXAttributes(), LoadMonitorMySQL\getLagTimes(), FileBackendStore\getLocalCopyMulti(), FileBackendStore\getLocalReferenceMulti(), LBFactoryMulti\getMainLB(), RedisBagOStuff\getMulti(), RawAction\getRawText(), LoadBalancer\getReaderIndex(), WikitextContent\getSection(), LBFactoryMulti\getSectionForWiki(), JobQueue\getSiblingQueueSizes(), JobQueue\getSiblingQueuesWithJobs(), RedisBagOStuff\incr(), RunJobs\loadBackoffs(), Exif\makeFilteredData(), FileBackendStore\moveInternal(), LBFactoryMulti\newMainLB(), Sanitizer\normalizeSectionNameWhitespace(), FileBackendStore\preloadFileStat(), FileBackendStore\primeContainerCache(), FileBackendStore\primeFileCache(), EditPageTest\provideAutoMerge(), PoolCounterRedis\release(), WikitextContent\replaceSection(), WikiPage\replaceSection(), WikiPage\replaceSectionContent(), RedisBagOStuff\set(), HTMLForm\setFooterText(), HTMLForm\setHeaderText(), SpecialSearch\showHit(), FileBackendStore\storeInternal(), FileBackendStore\streamFile(), RunJobs\syncBackoffs(), EditPageTest\testExtractSectionTitle(), EditPageTest\testSectionEdit(), MediaWiki\triggerJobs(), Exif\validate(), and wfStreamThumb().

◆ $sectionTests

$sectionTests = array( '3.4' )

Definition at line 86 of file Utf8Test.php.

◆ $success

◆ $test

◆ $total

◆ $verbose

Definition at line 39 of file Utf8Test.php.

Referenced by RefreshImageMetadata\execute(), and testLine().

◆ if

while (false !==($line=fgets($in))) if( $failed)

Definition at line 30 of file Utf8Test.php.

We use the convention $dbr for read and $dbw for write to help you keep track of whether the database object is a the world will explode Or to be a subsequent write query which succeeded on the master may fail when replicated to the slave due to a unique key collision Replication on the slave will stop and it may take hours to repair the database and get it back online Setting read_only in my cnf on the slave will avoid this but given the dire we prefer to have as many checks as possible We provide a but the wrapper functions like please read the documentation for except in special pages derived from QueryPage It s a common pitfall for new developers to submit code containing SQL queries which examine huge numbers of rows Remember that COUNT * is(N), counting rows in atable is like counting beans in a bucket.------------------------------------------------------------------------ Replication------------------------------------------------------------------------The largest installation of MediaWiki, Wikimedia, uses a large set ofslave MySQL servers replicating writes made to a master MySQL server. Itis important to understand the issues associated with this setup if youwant to write code destined for Wikipedia.It 's often the case that the best algorithm to use for a given taskdepends on whether or not replication is in use. Due to our unabashedWikipedia-centrism, we often just use the replication-friendly version, but if you like, you can use wfGetLB() ->getServerCount() > 1 tocheck to see if replication is in use.===Lag===Lag primarily occurs when large write queries are sent to the master.Writes on the master are executed in parallel, but they are executed inserial when they are replicated to the slaves. The master writes thequery to the binlog when the transaction is committed. The slaves pollthe binlog and start executing the query as soon as it appears. They canservice reads while they are performing a write query, but will not readanything more from the binlog and thus will perform no more writes. Thismeans that if the write query runs for a long time, the slaves will lagbehind the master for the time it takes for the write query to complete.Lag can be exacerbated by high read load. MediaWiki 's load balancer willstop sending reads to a slave when it is lagged by more than 30 seconds.If the load ratios are set incorrectly, or if there is too much loadgenerally, this may lead to a slave permanently hovering around 30seconds lag.If all slaves are lagged by more than 30 seconds, MediaWiki will stopwriting to the database. All edits and other write operations will berefused, with an error returned to the user. This gives the slaves achance to catch up. Before we had this mechanism, the slaves wouldregularly lag by several minutes, making review of recent editsdifficult.In addition to this, MediaWiki attempts to ensure that the user seesevents occurring on the wiki in chronological order. A few seconds of lagcan be tolerated, as long as the user sees a consistent picture fromsubsequent requests. This is done by saving the master binlog positionin the session, and then at the start of each request, waiting for theslave to catch up to that position before doing any reads from it. Ifthis wait times out, reads are allowed anyway, but the request isconsidered to be in "lagged slave mode". Lagged slave mode can bechecked by calling wfGetLB() ->getLaggedSlaveMode(). The onlypractical consequence at present is a warning displayed in the pagefooter.===Lag avoidance===To avoid excessive lag, queries which write large numbers of rows shouldbe split up, generally to write one row at a time. Multi-row INSERT ...SELECT queries are the worst offenders should be avoided altogether.Instead do the select first and then the insert.===Working with lag===Despite our best efforts, it 's not practical to guarantee a low-lagenvironment. Lag will usually be less than one second, but mayoccasionally be up to 30 seconds. For scalability, it 's very importantto keep load on the master low, so simply sending all your queries tothe master is not the answer. So when you have a genuine need forup-to-date data, the following approach is advised:1) Do a quick query to the master for a sequence number or timestamp 2) Run the full query on the slave and check if it matches the data you gotfrom the master 3) If it doesn 't, run the full query on the masterTo avoid swamping the master every time the slaves lag, use of thisapproach should be kept to a minimum. In most cases you should just readfrom the slave and let the user deal with the delay.------------------------------------------------------------------------ Lock contention------------------------------------------------------------------------Due to the high write rate on Wikipedia(and some other wikis), MediaWiki developers need to be very careful to structure their writesto avoid long-lasting locks. By default, MediaWiki opens a transactionat the first query, and commits it before the output is sent. Locks willbe held from the time when the query is done until the commit. So youcan reduce lock time by doing as much processing as possible before youdo your write queries.Often this approach is not good enough, and it becomes necessary toenclose small groups of queries in their own transaction. Use thefollowing syntax:$dbw=wfGetDB(DB_MASTER
the array() calling protocol came about after MediaWiki 1.4rc1.
List of Api Query prop modules.
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For updating the view updating the linked to tables after a etc PHP does not yet have any way to tell the server to actually return and disconnect while still running these but it might have such a feature in the future We handle these by creating a deferred update object and putting those objects on a global then executing the whole list after the page is displayed We don t do anything smart like collating updates to the same table or such because the list is almost always going to have just one item on if that
Definition: deferred.txt:11