3use Liuggio\StatsdClient\Entity\StatsdData;
4use Liuggio\StatsdClient\Sender\SenderInterface;
11 use MediaWikiCoversValidator;
17 $sender = $this->getMockBuilder( SenderInterface::class )->getMock();
18 $sender->expects( $this->any() )->method(
'open' )->will( $this->returnValue(
true ) );
20 $sender->expects( $this->once() )->method(
'write' )
23 $sender->expects( $this->never() )->method(
'write' );
25 if ( defined(
'MT_RAND_PHP' ) ) {
26 mt_srand( $seed, MT_RAND_PHP );
31 $client->send(
$data, $sampleRate );
35 $unsampled =
new StatsdData();
36 $unsampled->setKey(
'foo' );
37 $unsampled->setValue( 1 );
39 $sampled =
new StatsdData();
40 $sampled->setKey(
'foo' );
41 $sampled->setValue( 1 );
42 $sampled->setSampleRate(
'0.1' );
46 [ $unsampled, 1, 0 ,
true ],
47 [ $sampled, 1, 0 ,
false ],
48 [ $sampled, 1, 4 ,
true ],
49 [ $unsampled, 0.1, 0 ,
false ],
50 [ $sampled, 0.5, 0 ,
false ],
51 [ $sampled, 0.5, 4 ,
false ],
56 $matching =
new StatsdData();
57 $matching->setKey(
'foo.bar' );
58 $matching->setValue( 1 );
60 $nonMatching =
new StatsdData();
61 $nonMatching->setKey(
'oof.bar' );
62 $nonMatching->setValue( 1 );
64 $sender = $this->getMockBuilder( SenderInterface::class )->getMock();
65 $sender->expects( $this->any() )->method(
'open' )->will( $this->returnValue(
true ) );
66 $sender->expects( $this->once() )->method(
'write' )->with( $this->
anything(),
67 $this->equalTo( $nonMatching ) );
70 $client->setSamplingRates( [
'foo.*' => 0.2 ] );
73 $client->send( $matching );
75 $client->send( $nonMatching );
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for use
testSampling( $data, $sampleRate, $seed, $expectWrite)
samplingDataProvider
A statsd client that applies the sampling rate to the data items before sending them.
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such and we might be restricted by PHP settings such as safe mode or open_basedir We cannot assume that the software even has read access anywhere useful Many shared hosts run all users web applications under the same so they can t rely on Unix and must forbid reads to even standard directories like tmp lest users read each others files We cannot assume that the user has the ability to install or run any programs not written as web accessible PHP scripts Since anything that works on cheap shared hosting will work if you have shell or root access MediaWiki s design is based around catering to the lowest common denominator Although we support higher end setups as the way many things work by default is tailored toward shared hosting These defaults are unconventional from the point of view of and they certainly aren t ideal for someone who s installing MediaWiki as MediaWiki does not conform to normal Unix filesystem layout Hopefully we ll offer direct support for standard layouts in the but for now *any change to the location of files is unsupported *Moving things and leaving symlinks will *probably *not break anything
$data
Utility to generate mapping file used in mw.Title (phpCharToUpper.json)
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped noclasses just before the function returns a value If you return true
processing should stop and the error should be shown to the user * false
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php