@bd808: Does this error still appear after 2024-04-16 15:30UTC? If not, then this is likely a duplicate of T355644 (which reverted T352530 which I ideally would have never merged but lots of undocumented custom changes make it hard to foresee unwanted breakage).

Thanks. (Text in videos cannot be searched for, things in videos cannot be read by a screenreader software.)

I was not successful to contact the three affected users. Thus I ran UPDATE phabricator_user.user_email SET isPrimary = 0 WHERE address = "xxx"; UPDATE phabricator_user.user_email SET isVerified = 0 WHERE address = "xxx"; for the three affected accounts.

...and https://gerrit.wikimedia.org/r/plugins/gitiles/labs/tools/forrestbot/+/refs/heads/master/forrestbot.py#38 looks correct enough to my eyes to survive a switch from standard user to bot.

Good points, thanks, again! Changed.

I disabled Form 70 today (looks like I disabled Form 81 more than a year ago). As this was not marked as a Create or Edit form, this should only create an issue if it is linked somewhere for *creating* tasks but not for *editing* existing tasks. Let's see.

Thanks! I removed it from the form preamble: https://phabricator.wikimedia.org/transactions/editengine/maniphest.task/view/46/

Summary:

• Folks have experienced this both with Chrome and Firefox (and other browsers), thus not browser add-on/extensions (potential interception).
• Attached auth account (LDAP vs SUL) for the Phab user account is irrelevant.
• Phab ACL project membership (e.g. triagers or trusted-contributors) makes no difference.
• Payload: Cookies seem not the case either - while one machine had "interesting" cookie data the other one was as minimal as my cookie data sent.

Hmm, so which codebase or WMF team is this task about? @Isaac / @VirginiaPoundstone: Would you know maybe? Currently this task has no relevant project tags so it will not be found on a workboard but get forgotten... TIA!

Future Hatstall version has been deployed two months ago, so we could have another discussion about this (but maybe it's already enabled? Should likely check on an identity defined by activity on a mailing list or Gerrit where email addresses get indexed).

Hi @amastilovic, can you please associate one or more active project tags with this task (via the Add Action... → Change Project Tags dropdown)? That will allow to see a task when looking at project workboards or searching for tasks in certain projects, and get notified about a task when watching a related project tag. Thanks!

• https://phabricator.wikimedia.org/diffusion/NRDK fails because https://gerrit-replica.wikimedia.org/r/node-rdkafka is a 403; https://gerrit.wikimedia.org/r/admin/repos/q/filter:node-rdkafka lists nothing, git clone ssh://gerrit.wikimedia.org:29418/node-rdkafka.git fails with a 403, thus I ran sudo ./bin/remove destroy rNRDK
• WRES fails because could not read Username for 'https://github.com': No such device or address because https://github.com/wikimedia/wikimedia-research does not exist, thus I ran sudo ./bin/remove destroy rWRES (repo would now be https://gitlab.wikimedia.org/repos/sre/miscweb/research-landing-page but that's also archived)
• https://phabricator.wikimedia.org/diffusion/EHPR fails to mirror because: Unexpected object type from git cat-file

For the records, SQL query that was used:

I posted the DB query output (464 times: Phab task URL, title, assignee, author) in public P60752 (which offers a "View Raw File" option so data could be imported into a spreadsheet application by setting | as a delimiter character).
The very same list of tasks is https://phabricator.wikimedia.org/maniphest/query/Pha3X9Ry6g11/#R and "Use Results > Export Data" in the upper right corner allows e.g. exporting in CSV format, if that's more feasible.

@Bugreporter: That reply is not particularly helpful. :)

Switched the three repos from using K19 for an ssh:// URI to using K18 for an https:// URI. Let's see if that helps, if not I may just switch this off completely

Requested public project New-Engagement-Experiments has been created: https://phabricator.wikimedia.org/project/view/7107/

Hi @Clarasiir. This does not sound like something is wrong in the code base (a so-called "software bug"), but instead like a support request (how to change settings, questions how to do something, etc.).
As Wikimedia Phabricator is for bug reports, enhancement requests, and planning work, please check https://www.mediawiki.org/wiki/Communication and bring this up on the support desk - thanks for your understanding!

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)

@Liz: Quarry and bots are not AFD?

In T362406#9720340, @Dzahn wrote:

The list of hardcoded user names in there seems kind of arbitrary?

I just don't remember what we/I did months ago. :D I'll check my mail and try to remember

I'd like to stall this on the outcome of T361997 in upstream which might be a way better approach.

I'd like to stall this on the outcome of T361997 in upstream which might be a way better approach.

Reopening due to revert in T362689

This is due to T304540 in https://gitlab.wikimedia.org/repos/phabricator/extensions/-/merge_requests/25 according to the logs

Deployed on 2024-04-16

Deployed on 2024-04-16

Deployed on 2024-04-16

Deployed on 2024-04-16

Deployed on 2024-04-16

Hmm. You could uncheck the "Enable Media Viewer" option under "Appearance" on your Preferences page, in that case.

Assuming this task is about the QuickSurveys code base, hence adding that project tag so other people who don't know or don't care about WMF stuff can also find this task when searching via projects.

Assuming this task is about the QuickSurveys code base, hence adding that project tag so other people who don't know or don't care about WMF stuff can also find this task when searching via projects.

@CapitainAfrika Again: Please do not add random project tags. Please also do not prioritize tickets if you do not plan to work on them yourself. Please also do not subscribe folks if they did not explicitly agree on this. Thanks.