User talk:BryanDavis/Archives/2019

From Wikitech
Jump to navigation Jump to search
Warning! Please do not post any new comments on this page. This is a discussion archive See current discussion or the archives index.


Please rename my username to Ruyaba. Thanks. RUYABA (talk) 01:46, 27 January 2019 (UTC)[reply]

@RUYABA: Please create a Phabricator task tagged with and #ldap requesting the account rename. Renaming Developer accounts is unfortunately not quite as easy as renames on the main project wikis, so it may take some time to complete the request depending on which systems you have used your Developer account to interact with. --BryanDavis (talk) 16:01, 27 January 2019 (UTC)[reply]

mkdir -p && venv

Hi! About [1], I think it does. Using virtualenv:

   $ rm -rf www/
   $ virtualenv -p python3 ~/www/python/venv
   Running virtualenv with interpreter /usr/bin/python3
   Using base prefix '/usr'
   New python executable in /data/project/permission-denied-test/www/python/venv/bin/python3
   Also creating executable in /data/project/permission-denied-test/www/python/venv/bin/python
   Installing setuptools, pip...done.
   $ ls www/python/venv/
   bin/     include/ lib/

And using venv:

   $ rm -rf www/
   $ webservice --backend=kubernetes python shell
   If you don't see a command prompt, try pressing enter.
   $ python3 -m venv ~/www/python/venv
   $ ls www/python/venv/
   bin/        include/    lib/        lib64/      pyvenv.cfg

Running this command creates the target directory (creating any parent directories that don’t exist already).

Dalba (talk) 03:40, 4 March 2019 (UTC)[reply]

@Dalba: That's pretty cool. I will admit to not having tried it myself before I reverted your edit. I am not sure if making the need to create the directory structure explicit to the reader is more or less important than the number of steps we describe. If you feel strongly about removing the mkdir instruction I will not edit war with you over it. --BryanDavis (talk) 03:57, 4 March 2019 (UTC)[reply]

User Rights

Hi Bryan Davis, Please be requested to add autopatroller and shell user rights for me. Regards, ZI Jony (Talk) 19:30, 27 March 2019 (UTC)[reply]

@ZI Jony: shell user is a legacy right that actually does nothing with the current implementation of Cloud VPS. Is there a specific reason that you would need the autopatroller right? We generally only grant it on this wiki to users who have made many good faith contributions, and generally just to reduce workload on our patroller community. --BryanDavis (talk) 19:38, 27 March 2019 (UTC)[reply]
@BryanDavis: thanks for response. Shell user supposed to grant automatically when I was becomes a member of Toolforge project. Regarding Autopatroller right, on Phabricator I've stated work with several projects so it will reduce workload of patroller community when documented. Regards, ZI Jony (Talk) 20:08, 27 March 2019 (UTC)[reply]

geocommons/kml source

Hello BryanDavis. Thank you for the account activation. Please could you help me locate the geocommons/kml source code. SSH'ing in and running find / -name \*geocommons\* did not produce a result. Many appreciations, —Sladen (talk) 05:18, 29 June 2019 (UTC)[reply]

See also User talk:Para#License_and_publish_code_so_you_can_get_some_help_with_maintenance? and User_talk:Para#kmlexport (extra pings to Dvorapa and Para. This is for trying to work T226710 where geocommons/kml is missing the majority of images.
Sladen The source code you are looking for is somewhere under /data/project/geocommons/, but that tool's $HOME has permissions applied that keep everyone who is not a maintainer of the geocommons tool from seeing the files. Para is currently the only maintainer of geocommons (per --BryanDavis (talk) 22:09, 30 June 2019 (UTC)[reply]
BryanDavis, thanks. Had a reply today from Para over at commons:User_talk:Para#Geocommons/kml not showing most results; and have asked to be added as an additional maintainer at [2] in order to try and start debugging with a view to getting things fixed on a longer-term basis. —Sladen (talk) 20:01, 2 July 2019 (UTC)[reply]