I see

That extension does not appear to support PolyGerrit.

I've fixed it, your account is now in ldap.

I've updated a few bit's see

Work around is to do REQUESTS_CA_BUNDLE='' <command> i got docker-pkg 1.1.4 and 2.0.0 working with that.

This is the difference between 1.1.2 and 1.1.4 https://github.com/wikimedia/operations-docker-images-docker-pkg/compare/1.1.4...master

1.1.4 seems broken, where as 1.1.2 works. So something between 1.1.2 and 1.1.4 broke it.

@greg oh, really sorry, i missed your comment. Yup i am! @hashar seemed to address the comments (he merged the bazel image).

@MarkAHershberger i had to create the account manually using createAndPromote.php, i've sent the details through email for logging in.

We use MediaWiki 1.33 and the version of the extension is 0.1.2 (0919478121580061c41058c020432d47f35c3340)

You can add Hosts: <host> in the commit msg and run "check experimental".

@MarkAHershberger try again :)

Yup! (which is at https://gerrit.git.wmflabs.org/r/) i can make you an admin once you sign in (also need to register at https://ldapauth-gitldap.wmflabs.org/w/index.php)

I am seeing this:

Users are no longer added to the admin group in the ui, rather they are added to the gerritadmin ldap group.

Gerrit has been patched now, so this is now unblocked!

We can use gerrit slave feature for this (e.g a readonly). (gerrit2001 being the slave)

I just experienced this too. One minute it’s fast, the next it’s really slow.

I got this too on yahoo.

@Reedy Yes, I thought it was a bug before I spoke with upstream.

I’ve spoken with upstream who said that this is intentional due to the remove reviews right.

This seems like a bug, since you shouldn’t be able to remove a +2 after a change is merged, but it’s expected that you can remove votes after a change is merged.

I concur with ^^.

@Gilles oh, so your hitting T225308 ?

yup, found the commit that removes it on the master branch in MF, just not a easy back port as one of the files were renamed (https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/commit/eebdabe65c067dbcfd9ddf59ab283ddcdba61b40#diff-906c6ce0812fcfd8ccf583970a92df80)

When i looked earlier at https://gerrit.wikimedia.org/r/monitoring earlier, i saw nothing that would have explained this.

Turns out it was an issue on my side. I had

Cloning over https is also broken

@Gilles you can use the ldap password for the bot (for http auth). Just the ability to use a random generated pass was switched off.

curl https://gerrit.wikimedia.org/r/a/projects/mediawiki%2Fextensions%2F3D/branches/REL1_33 --user paladox:<pass> -X PUT
Branch "refs/heads/REL1_33" already exists

@mmodell using your ldap creds will work (i've done that before and simply curl --user <username>:'<pass>' http://gerrit.wikimedia.org/r/a/accounts/20after4 will work.

I’m wrong, it was removed from gerrit, but being re added in https://gerrit-review.googlesource.com/c/gerrit/+/226754

See https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/473643/

Gerrit 2.16 still supports Git protocol 2 (they just disabled it by default rather then enabled it by default). So we can enable once we upgrade.

For example if we removed:

@mmodell Yup, it may be installed but the php class manages the mods (removes ones that are not maintained by the class).

@mmodell could it be because we don't have php-mailparse installed when on stretch?

@greg this is not related to the reimage :) (i know why it's happening, it's due to upstream removal of some old configs) We never moved the "reply to email" config to the new syntax. I only moved it to allow the continuing of emails being sent. (https://github.com/wikimedia/puppet/commit/d45a46d7ee7fefc2552c03e2bb08c21667191341#diff-f0958b3f2f1547cbbd8476eaf38f82fc) (since i didn't know how to setup phab to receive email using the new syntax)

I think https://groups.google.com/forum/#!topic/repo-discuss/0yej8sQDcPo may be related. Also im leaning towards (based on the user reply in that thread) that this: