User talk:Yuvipanda

Stuck jobs at Tools

Your jobs #89887 and #89916 are stuck due to the error file problem. You should delete them (qdel 89887; qdel 89916), as I believe otherwise jsub may not schedule new jobs with the name sync. --Tim Landscheidt (talk) 02:17, 23 May 2013 (UTC)

Done! yuvipanda (talk) 02:32, 23 May 2013 (UTC)

Tool lab (mini-server)

You got access to local-wikiatlas2014 :) Yug (talk) 13:11, 11 May 2014 (UTC)

RSS feed to The Signpost is broken

hi the RSS feed to The Signpost on http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/Subscribe is broken and since you are the maintainer i add this post asking you to fix it. thanks a lot stof999

Completing project documentation

This is regarding the announcement (http://lists.wikimedia.org/pipermail/labs-l/2014-July/002762.html) if you have missed it.

We have added some fields in addition to description field which is already there on your projects. Please click "Edit Documentation" in your project page/ project pages and fill the blanks. It will only take few minutes from your valuable time.

If you have any comments or suggestion on the form please let me know.--Sandaru (talk) 17:27, 25 July 2014 (UTC)

dplbot webservice flaky again

The webservice for dplbot has been going non-responsive (even though the process appears to continue to run) repeatedly over the past 48 hours. I can restart it manually, but it always fails again fairly soon. The last entry in the service.log file is from 2015-06-04T09:24:05.392127. --russblau (talk) 13:38, 5 June 2015 (UTC)

Thanks

Thanks for helping me log into Tool Labs with Windows. I finally got the SSH authentication to work. Just downloading new ssh keys seemed to work. PuTTy's ssh generator was more helpful (for a Windows user) than . Thanks. Lucas559 (talk) 19:36, 16 July 2015 (UTC)

Make Notebooks on PAWS public?

Hi!

Great to see that one can use Jupyter Notebooks at WMF Labs! Thanks!

I intend to write Notebooks to share and explain how I produce the data for guides about stuff I do in the Connected Open Heritage project. Would you say it's a better idea that I create the Notebooks on PAWS, rather than locally and then share then on Github for others to view easily? Is there any additional goodies, like sharing access with other Wikimedia/Wikilabs users, publishing runnable Notebooks etc in PAWS that I should be aware of?

Regards, /Mattias Östmar (WMSE) (talk) 07:55, 10 June 2016 (UTC)

I seem to need the same thing. I notice there's a http://paws-public.wmflabs.org/paws-public/ now, but how do I get my jupyter notebook into the public directory ? --AbdealiJK (talk) 07:39, 14 September 2016 (UTC)

User:AbdealiJK sorry, just noticed it! You can get it at https://paws-public.wmflabs.org/paws-public/User:YOURUSERNAME. yuvipanda (talk) 06:58, 28 September 2016 (UTC)

A cup of tea for you!

:-) Gabrieloli (talk) 18:48, 27 September 2016 (UTC)

Force use user-config.py in current directory

Hi, I cloned pwb to my PAWS directory since I am not using the PAWS shared one. When I cd to the pwb dir and run a pwb.py login it does not take the user-config from the current directory but from the home (if there is none it defaults to test:wiki). Is there a way to make pwb use the user-config from the directory the pwb.py resides at? Thanks. --Wesalius (talk) 07:11, 20 October 2016 (UTC)

Best practice for setting up Python services at Tool Labs

Hi yuvipanda,

I'm currently looking into deploying an Python 3.4 Flask application at Tool Labs. I have seen a few diverse examples here at Wikitech, they are all different and not to easy to follow some using FCGI configuration and other using Kubernetes. I was hoping it would be possible to set it up without creating a new service group aka have it under abbe98tools/ without breaking existing tools which uses PHP.

What would be the best solution for setting this up, FCGI configuration or Kubernetes? Kubernetes seams to me as the easiest to learn.

Thanks --Abbe98 (talk) 13:44, 21 October 2016 (UTC)

Wikistream

Hi, do you know why wikistream is not working? Greetings Helfmann (talk) 11:07, 29 January 2017 (UTC)

Wiki Replica c1.labsdb to be rebooted Monday 2017-10-30 14:30 UTC

A tool you maintain is hosting data on labsdb1001.eqiad.wmnet (aka c1.labsdb). This server will be rebooted Monday 2017-10-30 at 14:30 UTC.

Normal usage of the *.labsdb databases should experience only limited interruption as DNS is changed to point to the labsdb1003.eqiad.wmnet (aka c3.labsdb). The c1.labsdb service name will not be updated however, so tools hardcoded to that service name will be interrupted until the reboot is complete.

There is a possibility of catastrophic hardware failure in this reboot. There will be no way to recover the server or the data it currently hosts if that happens. Tools that are hosting self-created data on c1.labsdb will lose that data if there is hardware failure. If you are unsure why your tool is hosting data on c1.labsdb, you can check the database and table names at https://tools.wmflabs.org/tool-db-usage/.

This reboot is an intermediate step before the complete shutdown of the server on Wednesday 2017-12-13. See Wiki Replica c1 and c3 shutdown for more information. --BryanDavis 00:21, 28 October 2017 (UTC)

Wiki Replica c3.labsdb to be shutdown Wednesday 2017-12-13

A tool you maintain is hosting data on labsdb1003.eqiad.wmnet (aka c3.labsdb). This server will be taken out of service on Wednesday 2017-12-13.

Normal usage of the *.labsdb databases should experience only limited interruption as DNS is changed to point to the new Wiki Replica cluster. The c3.labsdb service name will not be updated however, so tools hardcoded to that service name will be interrupted until they are updated to use a new service name.

Tools that are hosting self-created data on c3.labsdb will lose that data if it is not migrated to tools.db.svc.eqiad.wmflabs (also known as tools.labsdb). If you are unsure why your tool is hosting data on c3.labsdb, you can check the database and table names at https://tools.wmflabs.org/tool-db-usage/ or phab:P6313.

Please see Wiki Replica c1 and c3 shutdown for more information. --BryanDavis 20:36, 15 November 2017 (UTC)

dumpscan tool review

Hi, we're doing a review to make sure as many tools meet a minimum standard. I noticed dumpscan doesn't have a description on toolsadmin, licence or a published repo. Could you add these information to this tool? Thanks! Komla Sapaty (talk) 02:33, 8 April 2023 (UTC)

gerrit-patch-uploader review

Hi, we're doing a review to make sure as many tools meet a minimum standard. I noticed gerrit-patch-uploader tool doesn't have a published repo. Could you add this information to this tool? Thanks! Komla Sapaty (talk) 20:52, 5 July 2023 (UTC)

ios-crashes review

Hi, we're doing a review to make sure as many tools meet a minimum standard. I noticed ios-crashes doesn't have a description, licence or a published repo. Could you add these information to this tool? Thanks! Komla Sapaty (talk) 22:52, 5 July 2023 (UTC)

notebooks review

No repo, licence and description Hi, we're doing a review to make sure as many tools meet a minimum standard. I noticed notebooks doesn't have a description, licence or a published repo. Could you add these information to this tool? Thanks! Komla Sapaty (talk) 23:26, 6 July 2023 (UTC)

Tool Migration from the Grid

Hi yuvipanda, your tool is still running on the grid engine. According to the grid deprecation timeline that was shared, the grid will be stopped on the 14th of February. If you need assistance with the migration, kindly reach out on the phabricator ticket.

Please find the relevant ticket on Phabricator here T319787 Komla Sapaty (talk) 23:16, 1 February 2024 (UTC)