latest Elastica release does not include Elastica\Client?
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Nimworking
	Feb 26 2026, 12:20 PM

Description

Using the same working setup as I have used for a long time I got a error with latest release Elastica-REL1_42-af1c823.tar.gz
I get this error:

Error: Class "Elastica\Client" not found

Backtrace:

from /var/www/html/extensions/Elastica/includes/ElasticaConnection.php(97)
#0 /var/www/html/extensions/Elastica/includes/ElasticaConnection.php(68): MediaWiki\Extension\Elastica\ElasticaConnection->getClient()
#1 /var/www/html/extensions/CirrusSearch/includes/Connection.php(130): MediaWiki\Extension\Elastica\ElasticaConnection->setConnectTimeout(int)
#2 /var/www/html/extensions/CirrusSearch/includes/CirrusSearch.php(173): CirrusSearch\Connection->__construct(CirrusSearch\SearchConfig)
#3 /var/www/html/vendor/wikimedia/object-factory/src/ObjectFactory.php(240): CirrusSearch\CirrusSearch->__construct()
#4 /var/www/html/includes/search/SearchEngineFactory.php(69): Wikimedia\ObjectFactory\ObjectFactory::getObjectFromSpec(array, array)
#5 /var/www/html/includes/specials/SpecialSearch.php(843): SearchEngineFactory->create(null)
#6 /var/www/html/includes/specials/SpecialSearch.php(296): MediaWiki\Specials\SpecialSearch->getSearchEngine()
#7 /var/www/html/includes/specials/SpecialSearch.php(203): MediaWiki\Specials\SpecialSearch->load()
#8 /var/www/html/includes/specialpage/SpecialPage.php(728): MediaWiki\Specials\SpecialSearch->execute(null)
#9 /var/www/html/includes/specialpage/SpecialPageFactory.php(1717): MediaWiki\SpecialPage\SpecialPage->run(null)
#10 /var/www/html/includes/actions/ActionEntryPoint.php(504): MediaWiki\SpecialPage\SpecialPageFactory->executePath(string, MediaWiki\Context\RequestContext)
#11 /var/www/html/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()
#12 /var/www/html/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()
#13 /var/www/html/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#14 {main}

Related Objects

Mentioned In: T419505: openIDConnect does not bundle dependencies
T253588: extdist is not rotating logs
Mentioned Here: T253588: extdist is not rotating logs

Event Timeline

Nimworking created this task.Feb 26 2026, 12:20 PM

Restricted Application added a project: Discovery-Search. · View Herald TranscriptFeb 26 2026, 12:20 PM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

with latest release Elastica-REL1_42-af1c823.tar.gz

@Nimworking Could you please elaborate what makes you think that is the "latest" release, and where that file comes from?
1.42 is an unsupported insecure branch by now.

@Aklapper Sorry, i got the wrong version, it should be 1.43
When i say latest release its the latest file from here: https://extdist.wmflabs.org/dist/extensions

Correct name with the problem is:
Elastica-REL1_43-5fba34c.tar.gz

I tried v1.45 and got the same error, but i have not testet that version before so there might be a different root cause there

Aklapper changed the task status from Stalled to Open.Feb 26 2026, 2:58 PM

Just a little more information.
The vendor directory does not is not there in the .tar.gz files that i have problems with

as far as i know that is where 3-party dependency like Elastica\Client should be

Mschaap-vanboxtel subscribed.Mar 2 2026, 9:58 AM

@Reedy It looks like in 1.42 the vendor/ directory was included, but in 43-45 it was not. This feels like a change in the way mediawiki is packaged, but i didn't find anything in the release notes. Any ideas?

Nothing has changed in that sense; I imagine the extdist vm is doing something weird. Encountering an error or something building the vendor part running composer.

Not on a computer ATM, but will look later.

In T418469#11688882, @EBernhardson wrote:

@Reedy It looks like in 1.42 the vendor/ directory was included, but in 43-45 it was not. This feels like a change in the way mediawiki is packaged, but i didn't find anything in the release notes. Any ideas?

Just trying to give possibly helpfully information
I am 100% sure it used to be there in 1.43 before, but looking at the OpenIDConnect extension the tar.gz is updated around the same time and also missing vendor directory.

Reedy updated the task description. (Show Details)Mar 9 2026, 9:27 PM

I imagine this explains it:

Screenshot 2026-03-09 at 21.31.48.png (919×944 px, 241 KB)

reedy@extdist-06:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           394M   40M  354M  11% /run
/dev/sda1        20G   20G     0 100% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           1.0G     0  1.0G   0% /var/lib/nginx
/dev/sda15      124M   11M  114M   9% /boot/efi
/dev/sdb         22G   15G  6.1G  71% /srv
tmpfs           394M     0  394M   0% /run/user/0
tmpfs           394M     0  394M   0% /run/user/1226

Another instance of T253588: extdist is not rotating logs

root@extdist-06:/# ls -al /var/log/extdist
-rw-r--r-- 1 extdist extdist 12295168000 Mar  9 21:14 /var/log/extdist

Mentioned in SAL (#wikimedia-cloud) [2026-03-09T21:38:22Z] <Reedy> rm -rf /var/log/extdist T418469 T253588

Stashbot mentioned this in T253588: extdist is not rotating logs.Mar 9 2026, 9:38 PM

This *should* fix itself overnight when(ever) the nightly jobs run to build the latest tarballs...

In T418469#11690213, @Reedy wrote:

This *should* fix itself overnight when(ever) the nightly jobs run to build the latest tarballs...

Thanks!, its working for 1.43 now, but looks like 1.44 and 1.45 still have the same problem

Now i only get error from other extension with the exact same problem :)

Nimworking mentioned this in T419505: openIDConnect does not bundle dependencies.Mar 10 2026, 6:58 AM

Reedy merged a task: T419505: openIDConnect does not bundle dependencies.Mar 10 2026, 11:03 AM

You don’t need to open tasks for every extension when they all have the same underlying cause, which has been identified and fixed. The extension maintainer can’t actually do anything to fix it, as they’re not at fault.

It’s been broken for a week or two already, and it will take time for the infrastructure to catch up. I suspect until each repo has a new commit (for example, for localisation update, that happens once a week), a new package won’t be created.

So in most cases (for those repos with activity), this should be fully solved by the end of the week.

ok, thanks again and sorry for the extra trouble

	F72783300: Screenshot 2026-03-09 at 21.31.48.png
	Mar 9 2026, 9:32 PM

latest Elastica release does not include Elastica\Client?Closed, ResolvedPublicActions

Description

Related Objects

Event Timeline

latest Elastica release does not include Elastica\Client?
Closed, ResolvedPublic
Actions