Add the chart-renderer service to the list of trusted projects:

Here is the task for the symbol size and symbol shapes option in the chart definition:

The only remaining part of the chart definition to support is the interpolation option.

@Pietrasagh For the initial demo, we are limiting showSymbols to true and false, but will consider if/how we can support the other options for symbol size, line width etc.

So far, here is what the script can render :

the patch doesn't yet handle these options in the chart definition:

For building this as a node service, is it still recommended to use service-template-node? I noticed that it has some security issues, seems a bit outdated and not sure how well maintained it is.

alternatively, a new, separate project for multi-content revisions would be okay

interwikis work now among hifwiktionary and other wiktionary projects:

(re)populated the sites table.

this still happens :/

In T182326#3821144, @Addshore wrote:

In T182326#3821139, @daniel wrote:

@Addshore in which way would it be confusing? Who would be confused? What is test2wiki used for, specifically?

Test2 is primarily used to trial and debug global and cross-wiki features in conjunction with https://test.wikipedia.org and https://test.wikidata.org.
Test2 has been in gorup0 for rather a long time, and if people expect that and we change it, well, confusion follows.

Adding a wiki is not as easy as it should be, so I suppose Ladsgroup is trying to avoid that trouble. If it was easy, I would also opt for a new wiki with a more descriptive name... though I can't think of one off-hand.

@greg Both make sense, but making a new wiki is more overhead. The only reason to do that is to avoid confusion, as Adam says. Not sure how bad that confusion would actually be though.

If making a new wikis is too hard then lets use something we have, but I think a new site would be the 'best' option.

fixed by https://gerrit.wikimedia.org/r/#/c/394642/ (in review)

MediaInfo is no longer included in the build and we are killing the build anyway

@hoo ok :/

we had dispatch lag again today (enwiki especially lagged).

such css rule could be added to https://www.wikidata.org/wiki/MediaWiki:Common.css if this is something most users want. Otherwise it can be added to user css or maybe a gadget

@Krinkle is it okay for this to wait to go out w/ the train next week or should we consider a backport?

we can disable the notifications for wikibase changes sent to the clients

Wikidata.localisation.php uses $wgWikidataBaseDir, which could be set/managed outside the build

looks like the spam has stopped

we should check with @demon if git submodules will be okay with CI / deployment. While I think they might work, I vaguely remember there being some issue with having them in extensions with the deployment tools

looks like we also need to setup anti-spam measures on the wiki (we are getting spam users)

fixed the 502 error and the wiki works again.

can someone please add me to the wikidata-lexeme project on labs? If I am part of the project, then I can take a look at the issues / fix.

array_merge is the default config strategy:

hhvm error logs have "Fatal error: unknown exception"

I have a script for this:

fix for this goes out tomorrow (with the train/normal deployment schedule)

this is enabled again on test wikis (https://test2.wikipedia.org/wiki/Special:Version) and the fix goes out everywhere else with the train this week (tomorrow/thursday)

it's probably somethign in property suggester or one of those extensions

@hoo this issue / code never made it to production yet

I would like to fix this in swat tomorrow. I believe it only needs a change in the build, preferably i am able to verify locally + on beta