See mw:Bugwrangler for more information.
Member of Release-Engineering-Team. I am not a Product Manager.
See mw:Bugwrangler for more information.
Member of Release-Engineering-Team. I am not a Product Manager.
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!
aklapper@phab1004:~$ grep -r "Error while updating the" /var/log/phd/daemons.log.1 | grep "repository. {>} (CommandException) Command failed with error #255!" | cut -c 84- | sort -u Error while updating the "rEHPR" repository. {>} (CommandException) Command failed with error #255! Error while updating the "rNRDK" repository. {>} (CommandException) Command failed with error #255! Error while updating the "rWRES" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-animanga-db-matcher" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-api-docs" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-axel" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-botutor" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-contentcontributor" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-discord-irc" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-milhistbot-bd808-test" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-phabricator-bug-status" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-revi-kowikibots" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-vipbot" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-wikishootme" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-xtools-legacy" repository. {>} (CommandException) Command failed with error #255! Error while updating the "tool-ytcleaner" repository. {>} (CommandException) Command failed with error #255!
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.
I smell some user scripts under Local-Wiki-Template-And-Gadget-Issues here... https://ja.wikipedia.org/w/index.php?search=%22wpReason%22&title=特別:検索&profile=advanced&fulltext=1&ns2=1
@T34355635353565356463456347643 Please read and follow https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette if you would like to continue to be active here. Your tone is not welcome. Thanks.
If you do not want to "wait for an image", then your need to fix your internet connection. That is not Wikimedia's fault.
@Timi042: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@danshick-wmde / @darthmon_wmde : Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@danshick-wmde / @darthmon_wmde : Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@leila: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@Lhanars: Hi! This task has been assigned to you a while ago. Could you maybe share an update? Do you still plan to work on this task, or do you need any help? See also the previous comment here.
@tizianopiccardi / @Miriam: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@MunizaA / @KHernandez-WMF : Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@leila: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@sbassett: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@leila: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@diego: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@leila: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@leila: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!
@leila: Hi, the Due Date set for this open task passed a while ago.
Could you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved in case this task is done? Thanks!