No existing discussions now. Asked @Bennylin about this, replied, "artefact from the past. no longer used."

Advice from me: cleanup notepads that aren’t active (i.e. wasn’t accessed) for long, rather than brutally killing all past notepads. There must be many notepads that was created, and forgotten by anyone shortly after: such notepads exist while serve no actual purpose.

PHPUnit Prepare Parallel Run (Composer)
00:02:30.075 INFO:quibble.commands:>>> Start: PHPUnit Prepare Parallel Run (Composer)
00:02:30.553 > MediaWiki\Composer\PhpUnitSplitter\PhpUnitXmlManager::fetchResultsCache
00:02:30.553 
00:02:30.553 Unable to generate results cache URL - is LOG_PATH set?
00:02:30.553 
00:02:30.553 > MediaWiki\Composer\PhpUnitSplitter\PhpUnitXmlManager::listTestsNotice
00:02:30.553 
00:02:30.553 Running `phpunit --list-tests-xml` to get a list of expected tests ... 
00:02:30.553 
00:02:30.976 > phpunit '--list-tests-xml=tests-list-extensions.xml' '--testsuite=extensions'
00:02:31.080 Using PHP 7.4.33
00:02:31.081 Running with MediaWiki settings because there might be integration tests
00:02:43.430 PHPUnit 9.6.21 by Sebastian Bergmann and contributors.
00:02:43.430 
00:02:43.430 Wrote list of tests that would have been run to tests-list-extensions.xml
00:02:43.463 > MediaWiki\Composer\PhpUnitSplitter\PhpUnitXmlManager::splitTestsListExtensions
00:02:44.688 Encountered PHPUnit ErrorTestCase - check for a syntax error in the test suite or an error in a dataProvider!
00:02:44.689 Test suite splitting failed - falling back to linear run
00:02:44.689 Running extensions phpunit suite databaseless tests...
00:02:44.692 Running command ''composer' 'run' '--timeout=0' 'phpunit:entrypoint' '--' '--configuration' 'phpunit-database.xml' '--testsuite' 'extensions' '--exclude-group' 'Broken,ParserFuzz,Stub,Standalone,Database'' ...
00:02:45.865 > phpunit '--configuration' 'phpunit-database.xml' '--testsuite' 'extensions' '--exclude-group' 'Broken,ParserFuzz,Stub,Standalone,Database'
00:02:45.865 Could not read "phpunit-database.xml".
00:02:45.865 Script phpunit handling the phpunit event returned with error code 1
00:02:45.865 Script @phpunit was called via phpunit:entrypoint
00:02:45.865 Test suite splitting failed
00:02:45.894 INFO:quibble.commands:<<< Finish: PHPUnit Prepare Parallel Run (Composer), in 15.817 s

There's a such pipeline blockage in my latest patch. What should I do to address it?

In T329096#10711690, @gerritbot wrote:

Change #1134118 had a related patch set uploaded (by Unite together; author: Unite together):

[mediawiki/extensions/WikibaseLexeme@master] [Part of T329096] Reorganize objects in src/ to various locations to implement "hexagonal architecture" of OpenAPI.

https://gerrit.wikimedia.org/r/1134118

This patch above is an attempt to implement "hexagonal architecture" mentioned further above by @ItamarWMDE. It still has many many issues, and very likely to fail automatic tests. This is mainly because I'm unsure if some of those objects located in src/ are moved to correct locations. But I'm uploading it for now, as I'm really in need of some instructions to solve outstanding issues caused by this major adjustment.

@ItamarWMDE Should I change the structure of WikibaseLexeme extension to follow that of Wikibase package?

+2 by jenkins-bot on the patch above.

1125623: Created WblRestApi class, stubs for RouteHandlers and (some) route landler classes | https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseLexeme/+/1125623
Created this commit just now.

Sure, I'm attempting to work on this feature. Created a WblRestApi.php so far on my machine. My questions are as follows:

@ssr Hey, did you forget that Krassotkin no longer has access to phab here?

I also tested against the same template inside my userspace. Seems preload parameter doesn't work well with MediaWiki space pages.

Well, I asked @TheDJ and learned that there's actually no "team" as a whole and it has been unmaintained for quite long...

@Peachey88 Not yet. I thought it's sensible because this gadget has been used widely.

Currently there's a similar system on kkwiki. Maybe it's a good choice to apply the same tool onto ugwiki. Maybe I can do this. Though I'm not fluent in Uyghur, I know about its parallel writing systems.

Ja, it still happens in safe mode. Actually, it really appears everywhere as long as there is an interlanguage link on this page.

Here, just one example for jawiki, a page with REALLY long title:
https://ja.wikipedia.org/wiki/%E3%83%91%E3%83%A9%E3%83%99%E3%83%A9%E3%83%A0_(%E3%82%A4%E3%83%B3%E3%82%B0%E3%83%B4%E3%82%A7%E3%82%A4%E3%83%BB%E3%83%9E%E3%83%AB%E3%83%A0%E3%82%B9%E3%83%86%E3%82%A3%E3%83%BC%E3%83%B3%E3%81%AE%E3%82%A2%E3%83%AB%E3%83%90%E3%83%A0)

@Func Don't really know...

In T294554#7468359, @Jdlrobson wrote:

I cannot reproduce this one my self.