@Verdy_p Thanks for your very detailed explanation on this!

This bug does not reproduce on 1.36.0-wmf.10.

I've applied patch r/578298 and it seems the problem has been mitigated after purging the pages. Thanks in advance!

Yes, I have.

Just want to let you know now we have some dependency on the continuation support of action=query&list=geosearch XD (T95241 has been merged into this task)

I came here because this problem seems to be gone if I use a Bot Password (generated from Special:BotPasswords). That is, I have the following response sequence now, as long as I use a bot password to login

B --> format=json&action=logout
B <-- {}
A --> format=json&action=query&meta=userinfo&uiprop=blockinfo%7Cgroups%7Chasmsg%7Crights
A <-- {"batchcomplete":"","query":{"userinfo":{"id":6332,"name":"XuesongBot","groups":["bot","editor","*","user","autoconfirmed"], ...

which means logging out on the HttpClient B won't logging me out on the HttpClient A. While this is great and can facilitate my unit testing, I'm just wondering why the behavior can be such different. Do you have some explanation that may shed some light on this? Thanks!

I agree with @fantasticfears 's comments. Allowing user to mark a label in zh is not accurate enough. I even thought of, in an aggressive perspective, we should use zh-cn/tw/hk/mo/sg instead of plain zh-hans/hant, when specifying the label and description for an entity. After all, aside from fallbacks (e.g. zh-tw --> zh-hant), wikidata can automatically use, e.g. zh-tw label when a user request for zh-hant label, but there is no zh-hant label directly assigned to this entity.

I see. Thanks for your explanation, Thiemo!

In T182485#3824777, @Liuxinyu970226 wrote:

My guess is because in CLDR, the Simplified content are just using zh instead of zh_hans

Jeroen De Dauw replied in the mailing list:

It is not in use and never really was. (Code indicating it is not in use:
https://github.com/DataValues/Geo/blob/2d8e852d04318b13bd0db39b24afe7c56c61dc3e/src/Values/GlobeCoordinateValue.php#L193-L195
)

I'm not entirely sure why it is still in the API output and what the plans
with it are, but my guess is that it is still there for compatibility
reasons and that there is no intention of using this key in the future. If
I where creating an API client I'd just ignore this key.

In T177269#3653161, @Aklapper wrote:

I'm not quite sure where I should go if I were to have some general Wikibase (API) questions. Could you please give me some guidance? Thanks :-)

Please see the "Contact" section on https://www.wikidata.org/wiki/Wikidata:Main_Page

In T157185#2998927, @Liuxinyu970226 wrote:

So, what should be the actual output?

A

testB?

For now it's

A
:testB

which displays as
A
(Indented)testB
while what I want is just

A:testB