Thanks :)

All new groups created for repos in gerrit will now own them selfs. All existing groups need to request this so an admin can change this.

We removed the single group plugin. In gerrit the group has to own it's self for all members to be able to make changes to that group.

Caused by https://github.com/wikimedia/phabricator/commit/46d1596bf797890f9455147186f5e74369b5cec4#diff-557c601846b34231e7b04017c3b50cb7

Setting high as i doing want to be spamming especially people presuming aklapper is spamming which would not be true.

@MarcoAurelio yep for now. Seems to be failing with

Yep appears to be iPhone specific (I’ve only tested on iPhone so carnt speak for android)

I had this problem too and was just about to file a task.

Upstream is now invite only.

This is probably because we migrated to a new server. Replying to email is supported.

@Reedy they need to update that. I believe someone around wmf has been meaning to update it but did not find the source code to do that.

I think all new accounts with ldap was stopped a while ago. But old accounts can still use ldap. All new accounts are from mediawiki.

Im guessing when we fixed it it ran but did not get synced to the dumps server that day?

https://dumps.wikimedia.org/other/misc/ Also shows it too

Hi, there was some maintenance on that date. We migrated to the new server so there may need some tweaks.

I filled T172794

Your welcome :). I guess we can close this as resolved once we get your teammates added to the group? :)

requires https://gerrit.wikimedia.org/r/#/c/370645/

@Jhernandez hi, i know what you need to do to fix that. I will submit the patch.

GWTUI is being removed upstream. This looks some what done in polygerrit as you can click a button that shows the diff for all files without entering the file to see the diff, thus allowing you to write a comment when reviewing the diff.

Filled a new task upstream for polygerrit here https://bugs.chromium.org/p/gerrit/issues/detail?id=6964

All of this will be undone once GWTUI is removed. So this feedback will need to be aimed at polygerrit. Upstream are no longer taking any new features for GWTUI as 2.15 is about to be branched which then after GWTUI is going to start being removed (there's already a patch)

Please could you have a look at polygerrit to see if they may have fixed that there.

GWTUI is being removed upstream. Please could you have a look at polygerrit to see if that addressed your feedback.

Declining as gerrit 2.15 is about to be branch very soon possibly today and upstream are now planning the 3.x release. 2.15 is the last of the 2.x series. GWTUI is being removed in 3.x. If the problem happens in polygerrit please reopen or file a new task :)

we should probably only use @Aklapper email for /usr/local/bin/project_changes.sh on prod. I was testing /usr/local/bin/project_changes.sh and it sent it to him which then forwarded to the list without me realising.

the engine is configured for 3mb or 4mb one or the other. I got this error too.

In T137928#3505170, @jcrespo wrote:

can I ask which database is phab2001 connecting to right now?

php5-mysq has mysqli. i see no packages with the name php5-mysqli in debian https://packages.debian.org/jessie/php5-mysqli

+1 i see the bug. It should be scrollable.

viewing tasks and viewing repos this was also slow before the rsync started.

Is codfw ment to be slow? It feels slower then phab1001 when it had the phabricator-new domain.

I found https://phabricator-new.wikimedia.org/ continuously redirecting which then the browser short circuits it. But https://phabricator-new.wikimedia.org/diffusion/ works :)

This may now be possible as polygerrit is built from js and html not java a lot more people can contribute to do this :).

Yes but hhvm outputs it's version as 5.6.99 which would then hit the new version we are aiming for :).

gwtui is being removed so proposing this as declined since upstream are really no longer taking patches that fix anything gwtui unless it's critical or if it has to be done to get the feature to work in polygerrit too.

5.3 -> 5.5 was in the 5.x series 5.5 to 7.0 is a big change due to it have a new major version number 7. Though yes i see the point about maintaining things that are out of date. If we are going to do 7.0 then we would need to send an announcement in advanced :)

@Reedy that would be a big change going from 5.5 to 7.0. 7.0 is still rolling out even though 7.1 is out :)

Caused by https://github.com/wikimedia/mediawiki-extensions-Wikibase/commit/2987fe5bcf6223d03835670f7a6832e6a41a51ef

I believe most of this is done now :).