| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I5bb150ef8f019be59052f53950d033f54f36297d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The SwiftBackend theoretical max file size was increased to 5 GB
Sysadmins of MediaWiki are in a better position to judge what
is acceptable performance-wise for uploaded files than we are. The
answer presumably depends significantly on the hardware mediawiki
is running under. This increases the max limit to 32 GB (previously 4GB).
With files this big, operations such as copying and calculating SHA1
do become expensive. However everything still works, albeit with
some delay (I tested on a laptop with HDD, I imagine things are
significantly faster with an NVMe drive).
This changes the overall FileBackendStore limit which affects all
subclasses that haven't overriden the limit, including those from
extensions. Swift was set to 5GB as that backend has to change the
way it uses the Swift API for objects larger than 5GB.
This should not affect ordinary users as $wgMaxUploadSize is by
default only 100 MB in MediaWiki (4GB in Wikimedia).
Bug: T191805
Change-Id: Id091d51b620edbeea2d9df8c75422807bfc7aea0
|
|/
|
|
|
|
| |
Done in cf92cd08fd0132d0448fbfa8ac60981a9ddf59e3.
Change-Id: I750e564eceebd965234ae213b212b58d7523d44d
|
|
|
|
|
|
|
|
| |
This method is now redundant since rate limit checks are implicit in
permission checks. verifyPermissions() calls authorizeWrite( 'upload' ),
which will enforce any limits on the upload action.
Change-Id: I2ab3c646b8246411df501b548f652eaf11d0bc8e
|
|
|
|
|
|
| |
Bug: T348280
Depends-On: I3d2bd74cde12a9368a29f9afde2bc78e93ad1b7a
Change-Id: If0d6cd0f3a870fca406e5afbc9b49e3a4b2d30ab
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: T338775
Bug: T343451
Bug: T345656
Bug: T346697
Bug: T347345
Bug: T347445
Bug: T347906
Change-Id: I123c724f1300ea396cc8e4b44b2d3a968b162864
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "purge" permission was defined in $wgGroupPermissions, but not
checked in ActionPurge, SpecialPurge, or ApiPurge (until I9fee34f5b4).
The permission check for 'purge' was apparently lost in 2016 (see
I5749ff470d99). Ever since, we have been applying rate limits to
purging, but no permission checks.
Because of this, 'purge' should be declare to be an implicit right,
just like its sibling 'linkpurge'.
Note that the 'purge' permission was not granted to anon users per
default, yet RESTbase has Mocha tests that rely on being able to purge
pages without having to log in. Currently, CI tests for RESTbase are
broken because I9fee34f5b4 inadvertent restored permission checks for
'purge'.
Bug: T291316
Followup-To: I9fee34f5b44e947a00f1aaf2d28202d009e2caec
Change-Id: Iaceea6186a2216ae98118cb70a69ea20882fd982
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds new regex in BaseTextDiffer::localizeLineNumbers() to work with
wikidiff2 inline diffs as well as table diffs.
Since there are no "columns" in inline mode, we have a new message to
indicate how the line numbers changed from the old diff versus the new.
Deprecate DifferenceEngine::localiseLineNumbers() as no longer used and
redundant to BaseTextDiffer::localizeLineNumbers().
Bug: T346460
Change-Id: I7b195879b677e2242ad73070fe19ad82121576a8
|
| |
| |
| |
| | |
Change-Id: Iaff236f096c2b8a966da01479b80e98b76e80425
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting mTitle to null has been deprecated since 1.34.
Enforce this with a type declaration, now that this is possible in PHP 7.4.
To keep existing behavior, have getPage return null if mTitle is set
to Special:Badtitle/Missing. getTitle never returned null to begin with.
Change-Id: I2e0f87265f88ed6db97957af4faee8733e27df79
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Depends-On: If2a36938d5aacdf3bd4ac44cc6b097ddc2415b70
Depends-On: I7c670dd57296cf4add4ad1af941e1c3cf28a4e71
Change-Id: Iade89df3aa89d6fac5b783e4cbda73be1648c50e
|
|\ \ \
| |/ /
|/| |
| | | |
::getUltimateRedirectTarget, deprecated in 1.38"
|
| |/
| |
| |
| |
| |
| | |
deprecated in 1.38
Change-Id: I6564ff72c89ec47a680381edc298f0ffbf9bae60
|
| |
| |
| |
| |
| |
| |
| | |
Follows-up cac6a5260aa109b3.
Bug: T326454
Change-Id: Id7d90fe15f34afd8788d03f7ef2a3274a2f9a726
|
|/
|
|
|
| |
Bug: T335723
Change-Id: I530bae259291949e0f0853bb8bd8264acd131ff4
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This would simplify any caller that's trying to use extension1 cluster
Bug: T330590
Change-Id: Icccde8e10070686870601cae74b21ca9bed71ece
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The only reason for the callback was to check if a replacement
happened. We can do the same with the native $count feature.
Also inline a trivial sort() callback. It was effectively @internal
as it was obviously never meant to be used from outside of the class.
Both methods have been marked as public in I3588d9d. I think this
was just a mistake.
Change-Id: Ie33d4347f710fe227f9cbd8833c192c11d6e7c89
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
In line with our other PHP 8.x forward-looking dependencies.
Depends-On: I1fa21adbb8c6608b3b16f2bdbc5143b49764816c
Change-Id: I6e542b689dd20dd68140f7fc209530a998105945
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 20dbf6e3c942e5deec18a29c5951046123a791a3.
Reason for revert: T348134 is causing logspam
Bug: T348134
Change-Id: I03c9ff0a3f88c7e7ea55ac0af874446530063943
|
| |/ /
|/| |
| | |
| | | |
Change-Id: I030f7d8dbbe00d9283c75cdef056aaeb19f63967
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds Bcp47Code::isSameCodeAs() to the interface, which is
implemented for the Language class in
If3abc8a55eda8879ca904b25e9e3e5d40c1b0bab.
Depends-On: I323ebdf3bfa9f8fae2fb6991880cceae250dcf20
Change-Id: I34edabc5a3b6dc82810e8d96c7ce0513d6f18428
|
| |_|/
|/| |
| | |
| | | |
Change-Id: I946573bb17124198128ce471efb2965c53579fe5
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove unused methods:
https://codesearch.wmcloud.org/search/?q=%5CbmatchStart%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbmatchVariableStartToEnd%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbsubstituteCallback%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbgetVariableRegex%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbgetVariableStartToEndRegex%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbgetWasModified%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbaddArray%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbgetVariableRegex%5Cb
Mark internal methods as private:
https://codesearch.wmcloud.org/search/?q=%5CbgetRegex%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbgetRegexStart%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbgetVariableStartToEndRegex%5Cb
https://codesearch.wmcloud.org/search/?q=%5CbparseMatch%5Cb
There is probably more, e.g. the "add" method, but this is much
harder to prove.
Change-Id: I4093489b309105d2272535fb92135f5052f96ab6
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is difficult to distinguish this method from OutputPage::addJsConfigVars()
in code search:
https://codesearch.wmcloud.org/deployed/?q=%5BOo%5Dut%28put%29%3F%28%5C%28%5C%29%29%3F-%3EgetCategories%5C%28&files=&excludeFiles=&repos=
We generally try to replace $output with $parserOutput or $pOutput
as we touch code to improve the ability of codesearch to dig up
deprecated ParserOutput methods.
Bug: T305161
Depends-On: I02dd4f61c43c225b0ef6dc51c3e4f9d967a0a272
Depends-On: I61d2d77591579d825ad9d37f902e40366be55dd6
Depends-On: I91155106b7a9e10d3334f95ba4936d02851bfb11
Depends-On: Iaca745c79d9587571af03b23b21d76a6cba0ebf1
Depends-On: Id10a171c44411b1233ee4d6cf8fbd3dc57744eef
Depends-On: I47a25c011d9bd4b1a15dda4e673e32c25eb64f2b
Depends-On: I683fc768aba50b801f46467fcfa1668fa8731ea6
Change-Id: I5a2ac1c99b8b199102e12f0d32dd6ec5cdc24054
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Deprecated methods are:
* WebRequest::isSafeRequest()
* WebRequest::markAsSafeRequest()
Introduced in I43f4bc06c19d823d7d1f (549af8bf) and used in
I01ae2f045726208d2af7 (ce3a25be), then later removed in I4eb10817cccb40aa255
(e34fd634) which became unused in core.
As a result, it made markAsSafeRequest useless as there is really no
consumer at this point.
No known usage (confirmation) per our code search tool today. See below:
https://codesearch.wmcloud.org/search/?q=isSafeRequest&files=&excludeFiles=&repos=
Change-Id: I39cfb04c46374153d374fe0bb88690fa48ad7250
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The hook is no longer called, so the deprecation warning of the
HookContainer (as mention in DeprecatedHooks) cannot work as expected.
Change-Id: Idb586e9c2d8ba87411acc137537db6d6c75485a7
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Depends-On: I998b2166901c9436f3d06ebca06af21a7d199567
Change-Id: I9df31eb2f3ec25d532891d52668e44ecd4e6858e
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Depends-On: Ice678757aea2bb965f2b475faf647b07970dabe6
Change-Id: Ia9335ce5c13cab641b85fef8aa6f3db19f303b4d
|
|\| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Upgrading symfony/polyfill-php80 (v1.27.0 => v1.28.0)
- Upgrading symfony/polyfill-php81 (v1.27.0 => v1.28.0)
- Upgrading symfony/polyfill-php82 (v1.27.0 => v1.28.0)
- Upgrading symfony/yaml (v5.4.17 => v5.4.23)
Depends-On: Ibabde73873dcf0de42e78db574652caa59f7c772
Change-Id: I1751d9cda961b34621526f85e6c694c62f305643
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit cbde6b69deb702c51efdbbfee202eaf914a00495 to re-apply
the initial patch. This should only be merged once
I2acfd0b7a1e48aec107ded3bbe4963e2df24f4d3 is deployed.
Change-Id: If12ab65b1d773946fca6c8601ff51290136549c8
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
TitleArray is just a tiny little wrapper to TitleArrayFromResult,
so use the latter instead of the former. I have plans of killing
the former soon.
Change-Id: Ia06a6bb370ce313f38d3ec9a221ed7296aec0ee2
|
| |_|_|/ / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: T325959
Depends-On: I301cfecd95db04585e0f65b7919ea1c2e2bbff2a
Change-Id: I97938348407e3096187cfb41adb433a09ac77866
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Facilitate overriding the default CdxMessage
notice icon.
Bug: T300273
Change-Id: If51bc977e0cb42cfe9800caaf6a789a041d22e5c
|
|\ \ \ \ \ \ |
|