| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
|
|
|
|
|
| |
Use this to prevent deleting new RC entries at the title of page
deletion that were created since the deletion. This is useful if
an event performs a deletion and makes a new RC entry or if there
is high job queue lag.
Change-Id: I20f6a4aa0a660a24583c1d71f825b73daa748a24
|
|
|
|
|
| |
Bug: T137280
Change-Id: I78ee489f10e796d2b3fa39dcb4f65f0763860bf3
|
|
|
|
|
|
|
|
|
|
| |
Since LinksUpdate::doUpdate() already flushes the transaction,
go ahead and flush before other DataUpdates might run (e.g.
from RefreshLinksJob). Also release the lock before running
the LinksUpdateComplete handlers, as the lock is just to keep
LinksUpdate instances from racing with each other.
Change-Id: Ied97fa36fbca0203123e9fc966d2e23bfd621c0e
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: T95501
Change-Id: Ib0c911b030ae17cb7b0729be223b89d64c8c4b3f
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Similar to getTriggeringUser(). Also propagate it
to subjobs similarly.
Bug: T135959
Change-Id: I3d894acaf3d85b790e5034c7d9f76bf94672f445
|
|/
|
|
| |
Change-Id: I05787b6e9ace26e7a20c228fbc3502983dfed777
|
|
|
|
|
| |
Bug: T135690
Change-Id: If79ca385884f422e5ed11e77b29033c8cabf494c
|
|
|
|
|
| |
Bug: T134535
Change-Id: I73e22606e86b4db1bc9bf2cb12b9605507ffe2c2
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should avoid erratic lag spikes that happen as many links are
added and removed via new pages (sometimes bot generated) and edits
that blank pages as well as their reversions.
In the common cases of a modest number of link changes, the entire
update will still happen in one transaction. In any case, link updates
now use a lock to avoid clobbering each other on the same page.
Bug: T109943
Change-Id: Icd453fcc3d28342065893260ad327eae11870245
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ida563b29b5450c44358155fc937cd7eeb87090c2
|
|/
|
|
| |
Change-Id: If10840c5df849455027b5a497097e583fb982a65
|
|
|
|
| |
Change-Id: Icef1ecbed3d831557e0256fdfa53743b194007cc
|
|
|
|
| |
Change-Id: If55ddf441de69189c7fcdd3440f899c6b14f690f
|
|
|
|
|
|
|
|
|
|
| |
Per wikitech-l consensus:
https://lists.wikimedia.org/pipermail/wikitech-l/2016-February/084821.html
Notes:
* Disabled CallTimePassByReference due to false positives (T127163)
Change-Id: I2c8ce713ce6600a0bb7bf67537c87044c7a45c4b
|
|
|
|
|
|
| |
Closures support $this as of PHP 5.4
Change-Id: I2632d0c2bdc9e2fec72f1c64c3868dcb442ba871
|
|
|
|
|
|
|
| |
* Also create EventRelayerGroup class and config
Bug: T97562
Change-Id: Id7c9b0deb0ffd21277572a8e6407f87be6931a4d
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I269199f65ffc6ad50d16cb984c28b51a815e9a8f
|
|/
|
|
|
|
|
| |
This makes it easier to have deferred atomic DB transactions
Bug: T122115
Change-Id: I67afe335f03cc21fdce78abdf3f31fa67a368419
|
|
|
|
| |
Change-Id: I3fd87908c2a493fae49de6a29efe79f8d433c112
|
|
|
|
| |
Change-Id: I433acc7990a5fcefd0d2ff5b14ba33dec0424706
|
|
|
|
|
| |
Bug: T121228
Change-Id: I33addea4261d58cc93ab739621481065eb9c908d
|
|
|
|
|
| |
Bug: T113192
Change-Id: I89deb4f8143c1cc6154cdd05bcee1f49d3e3a75a
|
|
|
|
| |
Change-Id: Idcc528daf28e119349155d36e30a9bcf61b2e7d5
|
|
|
|
|
|
| |
Squid is not the only possible CDN
Change-Id: Ie2a2955847c5706e630322bbbab71c9d063b378f
|
|
|
|
|
|
|
| |
* These calls and methods should no longer be needed
* Follow-up to 6dedffc2d7f8
Change-Id: Iff121263610117112c84edb5e575f039456d1ac8
|
|
|
|
| |
Change-Id: I7f2ad8190e1a746b6c39190b86fa9c83c5b921fe
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* DeferrableUpdate classes can implement MergeableUpdate.
Duplicate updates will be merged via the merge() method.
* Make SquidUpdate support merge() so that duplicate URL
purges are now caught accross the entire pre-send request
execution.
Change-Id: Idffdd3e71d89e4a0f28281e65a881113caae497c
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* PRESEND/POSTSEND constants can now be used in addUpdate()
and addCallableUpdate() to control when the update runs.
This is useful for updates that may report errors the client
should see or to just get a head start on queued or pubsub
based updates like CDN purges. The OutputPage::output() method
can easily take a few 100ms.
* Removed some argument b/c code from doUpdates().
* Also moved DeferrableUpdate to a separate file.
Change-Id: I9831fe890f9f68f9ad8c4f4bba6921a8f29ba666
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* This puts these updates behind the JobRunner lag checks
* Made HTMLCacheUpdateJob::newForBacklinks() method, which,
along with lazyPush(), obsoletes this class.
Bug: T95501
Change-Id: I934de63bb6fe9e9b7abae157f0b3b2dbfd3188e1
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Recursive link updates no longer mention an category changes.
It's hard to avoid either duplicate mentioning of changes or
confusing explicit and automatic category changes.
* LinksUpdate no longer handles this logic, but rather WikiPage
decides to spawn this update when needed in doEditUpdates().
* Fix race conditions with calculating category deltas. Do not
rely on the link tables for the read used to determine these
writes, as they may be out-of-date due to slave lag. Using the
master would still not be good enough since that would assume
FIFO and serialized job execution, which is not garaunteed.
Use the parser output of the relevant revisions to determine
the RC rows. If 3 users quickly edit a page's categories, the
old way could misattribute who actually changed what.
* Make sure RC rows are inserted in an order that matches that
of the corresponding revisions.
* Better avoid mentioning time-based (parser functions) category
changes so they don't get attributed to the next editor.
* Also wait for slaves between RC row insertions if there where
many category changes (it theory it could well over 10K rows).
* Using a separate job better separates concerns as LinksUpdate
should not have to care about recent changes updates.
* Added more docs to $wgRCWatchCategoryMembership.
Bug: T95501
Change-Id: I5863e7d7483a4fd1fa633597af66a0088ace4c68
|
| | |
| | |
| | |
| | |
| | |
| | | |
instead lazy load WikiPage, when needed.
Change-Id: If67057b0b76f0f889ed498d8bbedaaeae3b2785d
|
| | |
| | |
| | |
| | |
| | |
| | | |
and rename the private method to be more clear
Change-Id: Iec7b934babddd102402cfa7616accd91fd3422ff
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
If the SearchEngine does not support search-update, then
$indexTitle is not used and thus no need to create it in
that case.
Change-Id: I487d06274e921223a3bcb5af846b48b7c2b8065e
|
|/
|
|
|
|
|
| |
A few random callers were calling doUpdate() themselves
instead of using DeferredUpdates
Change-Id: If121e6afab9899dae92f0bf831b0b0c9967deeb5
|
|
|
|
| |
Change-Id: Ia5b8060e8a93f40a2e31272e043b225f59fb6d50
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This causes it to add history, and trigger the TitleSquidURLs hook.
Bug: T116095
Change-Id: I41ebd2f34347a3f218f7d0bfc8962d286b943c16
|
|/
|
|
|
|
|
|
|
|
|
| |
Do the LinksUpdateComplete hook updates in a separate
transaction as they may do slow SELECTs and updates.
A large amount of DBPerformance warnings were triggered
by such cases.
Bug: T95501
Change-Id: Ie4e6b7f6aefc21bafba270282c55571ff5385fe0
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: T117860
Change-Id: I8c730a434b8bdda7664fd1e3bb3fbc8840804950
|
|/
|
|
| |
Change-Id: Ica2b8dce0978818a2f51684b97c93a3ba845d81a
|
|
|
|
|
|
| |
Also fixed various $wgMemc related comments
Change-Id: I20602b672f724c8df1e82bbe3c586cb899a54640
|