User talk:BDavis (WMF)

Previous discussion was archived at User talk:BDavis (WMF)/Archive 1 on 9 September 2015.

This talk page is not a Cloud VPS or Toolforge support forum. Contact information for Cloud VPS and Toolforge can be found at wikitech:Help:Cloud Services communication.

I would like to update vendor files via the composer update command in the Toolforge server, and an error appears

Update of wiki-connect/mediawiki-api failed The following exception is caused by a process timeout Check https://getcomposer.org/doc/06-config.md#process-timeout for details

In Process.php line 1204:

 The process "rm -rf '/data/project/gergesbot2/WikipediaBot/vendor/wiki-connect/mediawiki-api'" exceeded the timeout of 300 seconds.

I tried to delete a folder but it didn't work. Do you know the cause of the problem?

I guess good job for tracking me down, but asking me to personally debug your problems with Toolforge is not something that can reasonably scale to the entirely of the Wikimedia technical contributor community. I would invite you to ask questions like this via one of the official Cloud Services support channels.

When you do ask in one of those areas, please also include where you are running the command from (a specific Toolforge bastion? inside a `webservice shell` session? a scheduled job? some other means?). If you are attempting to run commands like this directly from a bastion the per-user process quotas applied on bastions may be causing file system operations to be slower than one would typically expect.

I have sent you a mail via "Email this user".<br>Acagastya (talk) 17:42, 3 July 2017 (UTC)

Sidenote: There is a user-preference (default-on) for us to get web-Notifications about any "Email from other user", so it is no longer necessary to send talkpage notes about this. :-)

@Quiddity (WMF): Due to a broken JavaScript gadget I was using, I could not see notifications for almost two months. It is better to leave a message, I think.

@AcagastyaI think I described what you need to do fairly completely in phab:T164910#3271720. The advice you have been given in #wikimedia-cloud^connect has been mixed in part because using NodeJS to write bots is not completely common and in part because you have not referenced the previous communications. What you want to do is possible. See Amir's offer to work with you in phab:T169338#3396104 for one way you might get help beyond the instructions I have already written and the documentation at wikitech:Help:Tool_Labs/Kubernetes#Kubernetes_continuous_jobs

Hi BDavis! Do you know a good 15 hour task I could work on to help contribute to Toolhub?

You might find one or more of the tasks at https://phabricator.wikimedia.org/maniphest/query/j8qhBnA1U9Lr/#R interesting. These are tasks that @SStefanova (WMF) proposed for people who were interested in working on Toolhub during the Hackathon this past May.

Yeah I saw those. Ok thank you.

Toolhub is an onion with many layers :) What are you specifically interested in contributing to/learning? Frontend, backend, search functionality, i18n...? Or is there any missing feature you yourself would like to see added?

Actually, I was just looking for a Python project to work on in Wikimedia for a school project and since I recently learned about Toolhub, I thought of working on it since it is a Django project . However, I learned the Django is actually just a backed framework and really you'd be coding Vue instead mostly which wouldn't work for the project.

Thank you anyways though. I definitely will continue to look into improving Toolhub in the future as I would like to eventually migrate our list of Tools at Wikidata to Toolhub. I imported all of the userscripts in there, but stopped when I realized that Toolhub doesn't support multilingual tools yet so that is the main breaker at the moment.

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:17, 4 January 2022 (UTC)

Striker now creates GitLab repos and prior Diffusion repos have been migrated. More at https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/LSUIQGQ4DCHNDDIT54XMQ2FHK4E4DW3W/

Hey. Dropping this here because… well, because I have no clue where would be more appropriate. And the same goes for this ping: @TCipriani (WMF). On both counts: apologies for the possibly misdirected interruption. :)

Anyways… What's the story on Toolforge and the Wikimedia GitLab instance?

The context is that I recently "inherited" a tool on Toolforge where the single original maintainer is no longer active, and it's been untouched since 2015. Lot's of Python 2 -> 3, new pywikibot, cleanup of single-maintainer idiosyncrasies, general modernisation, etc. is the order of the day. And since the original code is in a personal Github repo: migrating to a new repo!

And then I get tipped off to the existence of GitLab / https://gitlab.wikimedia.org. And in my primitive "Monkey see goodie, monkey want goodie!" brain, that sounds like the best of all possible goodies: <s>no Gerrit</s>the features of Github, but integrated in the MW/WMF ecosystem (auth, not least).

But them docs… Going by the docs it looks like the WMF GitLab is both currently fully ready for production, we just need to move everyone over to it; and still in testing and we shouldn't put anything of value in it; and in some kind of early-adopter / use for personal stuff phase.

And nowhere, not in the docs not in the consultation, do I see Toolforge mentioned.

And Toolforge, to my mind, is the perfect case for this. Lots of contributors that would flat out refuse to use Gerrit no matter what incentive you gave them, can't be dictated to on such things in any meaningful way, but who we really really want to use version control somewhere we (we = the movement) have some sort of visibility and consistency. And Toolforge has lots of groupings (tools) with members (maintainers) etc., already managed through a management interface (Striker).

So when reading through GitLab/Policy I immediately think each "tool" on Toolforge should get a project (and default repo) on GitLab, either automatically or by checking a checkbox in toolsadmin. Maintainers of the tool should automatically be maintainers on the GitLab project. Toolforge should have its own namespace on GitLab, with sub-namespaces for each tool? Anyway, that sounds like it wouldn't just be sweet but even "sweeeet!", and clean up a lot of code access and revision control headaches for Toolforge.

So… Is anybody talking to somebody about Toolforge and GitLab?

Is GitLab ready for ad hoc use for Toolforge tool maintainers? And if so, how in the heck would I actually do that? Or should I just go to Github and plan to migrate later?

And nowhere, not in the docs not in the consultation, do I see Toolforge mentioned.

That's an excellent point.

So… Is anybody talking to somebody about Toolforge and GitLab?

Not explicitly. We should put it on the Roadmap somewhere, even if it's at the end.

Is GitLab ready for ad hoc use for Toolforge tool maintainers? And if so, how in the heck would I actually do that? Or should I just go to Github and plan to migrate later?

The GitLab Roadmap should be up-to-date.

I would say you can use GitLab for your own personal projects, but it's going to be missing some niceties for a bit. The current thing it's missing is shared runners for CI (you can setup your own, but that's not our plan for the future). Hopefully that will be solved Soon™.

You can sign in to GitLab with a Wikimedia Developer account and use it as you would Github (with the exception of having CI which I'm aware is a big exception and hopefully very temporary).

I don't think CI is going to be too relevant for most Toolforge projects (I may be wrong). Certainly not for mine: I need a git repo with a nice web frontend for managing merge/pull requests, browsing commits, etc.; and some way to add the other maintainers for the tool (as set in Striker). My biggest concern looking at the docs was fitting those needs within the policy for namespaces etc. and whether "personal" really means personal (I'm seeing a lot of "This is my .bashrc" there), or just "not ready for mediawiki/core yet". Toolforge tools are kinda somewhere inbetween those extremes.

But in any case… A. Nyone and S. Omebody needs to start talking about just how good friends Toolforge and GitLab are going to be, and figure out who does what and when it makes sense. Unlike Gerrit->GitLab, which has some pretty significant drawbacks for at least some people, Diffusion->GitLab for Toolforge looks like all upside from where I'm sitting. A quick win, and one that helps the community more in the short term than the big migration from Gerrit. Especially if Paladox is right that the conversion on the Striker side isn't all that complicated (cf. T224676).

phab:T224676 is probably the correct place to discuss. My personal answer is that yes gitlab and Toolforge should be friends, and this will eventually replace the current support built into Striker (https://toolsadmin.wikimedia.org/) for creating per-tool Diffusion repositories. What I cannot say at all today is when GitLab will be "ready" to take this usage and when anyone will have the time to work on integrating Striker with GitLab.

Striker now creates GitLab repos and prior Diffusion repos have been migrated. More at https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/LSUIQGQ4DCHNDDIT54XMQ2FHK4E4DW3W/

A "not invented here is bad" attitude is fairly unhelpful in solving technical problems. Where does one stop in a journey down the stack in the name of self-control?

When I'm compiling the assembly by hand, damnit.

Thank you for everything you do for the Wikimedia community. You're awesome. ^>^ Pavithraes (talk) 19:39, 15 September 2020 (UTC)

om nom nom! I'm not likely to get real stroopwafels until we can all travel again, so I will cherish these virtual ones.

Report bugs in Magnus' tools at https://bitbucket.org/magnusmanske/

Hi. en:Wikipedia:PetScan is down again, and has been for some days; I wonder if this is related to https://phabricator.wikimedia.org/T251567 ? Could you possibly take a look at this?

Upstream bug report with Magnus is at https://bitbucket.org/magnusmanske/petscan/issues/163/petscans-down. I can only blindly restart this software, not fix any of its problems. Restarting it seems to only make things better for a few minutes or hours. Magnus needs to work on this software or recruit someone else to take it over or at least co-maintain it with him. There is really not much that I can usefully do to support the application.

Report bugs in Magnus' tools at https://bitbucket.org/magnusmanske/

I'm reffering to this one. I've tried to use it from two different computers but always get this "Not Found" page. Is it just me or is this an ongoing issues that hasn't been resolved for a while? (I'm contacting you about this because the error message mentions contacting the project administrators and mentions you).

If you are ending up on the page you linked that sounds like a bug in the URLs generated by pagepile. That is one of Magnus' tools according to https://tools.wmflabs.org/admin/tool/pagepile. His enwiki user page recommends reporting issues at https://bitbucket.org/magnusmanske/

Hello, I created a new tool (https://toolsadmin.wikimedia.org/tools/id/holidays-viewer) about 5 hours ago and I'm getting an error when I run become holidays-viewer. I've tried logging in and logging out several times but I'm still getting an error.

jeropbrenda@tools-sgebastion-07:~$ become holidays-viewer
become: no such tool 'holidays-viewer'
jeropbrenda@tools-sgebastion-07:~$ id
uid=21205(jeropbrenda) gid=500(wikidev) groups=500(wikidev),50380(project-tools),54127(tools.holidays-viewer)

What could be the problem?

Probably related to the issues we have been having with the background process that creates the new tool directories and credentials. This service was restarted 2019-08-05T16:10:23Z which I would hope has made it provision your tool correctly.