You are browsing a read-only backup copy of Wikitech. The live site can be found at

User talk:Para

From Wikitech-static
Revision as of 09:09, 19 August 2018 by imported>Dvorapa (→‎kmlexport: thank you)
Jump to navigation Jump to search

Your shell access was granted

Hello, welcome to Wikimedia Labs! I would like to inform you that your shell request was processed and you should be able to login to Bastion host now at In case you get into troubles, please read this page which contains useful information about accessing instances. You can also ask in our irc channel at #wikimedia-labs connect or send an e-mail to our mailing list - thank you, and have fun using labs! Tim Landscheidt (talk) 20:21, 24 June 2014 (UTC)

Welcome to Tool Labs

Hello Para, welcome to the Tool Labs project! Your request for access was processed and you should be able to login now via ssh at To get started, check the help page and the migrating from the Toolserver page. You can also ask in our IRC channel at #wikimedia-labs connect or send an e-mail to our mailing list – thank you, and have fun using Tools! Tim Landscheidt (talk) 20:21, 24 June 2014 (UTC)

Request for source code

Hello Para, we are forever in debpt for your great geo tools. Since I was curious, I noted that you have set permissions in a way that I am not able to view any of the source codes in

According the the labs policy, all tools must use an OSI approved open source license. Which one is your tool licensed under? Would it be possible to provide me with a copy of the scripts your kmlexport tool makes use of? Thanks in advance.

The reason I am asking is a simple: Images from HTTP are loaded on an HTTPS connection, using for example this query. Perhaps just fix that and I am silent :) -- Rillke (talk) 18:04, 14 July 2014 (UTC)

A few issues there:
  1. Google Maps doesn't support protocol relative links in kmz files. They are interpreted as links to embedded content.
  2. Your link asks Maps to get the kml over http.
  3. The Tool Labs proxy seems to be redirecting requests to, so the tool never knows the user was on https.
Here's another link that works around these issues. I'll have to have a think about the licensing. --Para (talk) 01:14, 24 July 2014 (UTC)
Oh nice, the graphics are now loaded over HTTPS with a HTTPS tool labs link. Thank you. I know about the labs proxy issue -- I think I've solved this sniffing some headers -- and Commons is explicitly setting a secure parameter to true if the user is on HTTPS on Commons. -- Rillke (talk) 07:29, 24 July 2014 (UTC)

Google maps classic has been turned off

Hi Para,

Google Maps Classic has been turned off today. Could you adjust the KMLexporter so that when it triggers a download, the downloaded file already has the .kml file extention in its name? This way it's easier to get a map into Google My Maps. Thank you. --1Veertje (talk) 14:19, 3 March 2015 (UTC)

Done. --Para (talk) 18:25, 3 March 2015 (UTC)
Thank you. Could it be that the section variable now doesn't work any more? --1Veertje (talk) 09:29, 5 March 2015 (UTC)
A, I see the whole tool is (temporarily?) off line. --1Veertje (talk) 09:30, 5 March 2015 (UTC)
The Tool Labs web service keeps dying every now and then, until the Bigbrother service kicks in and starts it again. Never happened on the Toolserver... The section feature still works, it was just the downtime causing problems. --Para (talk) 12:09, 5 March 2015 (UTC)

Moving kmlexport to trusty?


kmlexport has been dying a lot recently, and I think moving it to trusty will help (access to more RAM, to start with). However, it doesn't seem to work with newer versions of perl / other tools on trusty, and might need some massaging. Think you can help test it out (just do 'webservice2 start instead of webservice start') and move to trusty? I'll help in whatever way I can (am one of the tools admins). Thanks! yuvipanda (talk) 07:08, 13 March 2015 (UTC)

Alright, it looks fairly happy there now. I'll keep an eye. --Para (talk) 14:54, 14 March 2015 (UTC)

Commons:Special:NewFiles results in http 5xx in production

Hi Para, we (techops) have been experiencing some elevated http 5xx errors in production for thumbnails having as referral. The number of 5xx is sometimes enough to trigger our alarms, also I believe there might be race conditions with asking thumbnails right away after a file upload. However since some time we pre-generate certain standard thumbnail sizes (wgUploadThumbnailRenderMap in mediawiki-config) at upload time, specifically 320px, it would be nice to default to that size to avoid a couple of issues. Namely the 5xx errors and avoid generating non-standard thumbnail sizes and thus save space on media storage.


Filippo Giunchedi (talk) 12:27, 22 September 2015 (UTC)

The errors may have been due to the tool ignoring $abbrvThreshold and offering long thumbnail URLs. It doesn't anymore, so I hope that clears them. I've also changed to the default thumbnail size, but I might roll back if someone gets worried about the ~seven fold increase in downloads. is another example with non-standard thumbnail sizes, although it requires user input to continue generating the thumbs. I doubt either of these is very widely used. --Para (talk) 19:45, 22 September 2015 (UTC)
thanks a lot, that has helped! I'm not seeing any 5xx with your tool so far! ----

License and publish code so you can get some help with maintenance?

Para I recently started working on a long term project to help Tool Labs authors scale and support their tools as they become more widely used. I would like to work with you to resolve some of the issues discussed at phab:T92963#2264687 so we can get you some help with maintaining your kmlexport tool. I think the necessary first steps are to license and publish the source code for the tool. Once the code is public we can try to find people who are interested in helping you work on the stability and resource consumption issues. --BryanDavis (talk) 17:04, 4 May 2016 (UTC)


Hello, I would like to co-maintain your tool kmlexport. Currently I have a patch for some encoding issues with your tool and I would like to watch over the tool as this tool is still important for cswiki and dewiki (and probably frwiki and enwiki and some others too). I run my patch on, but this splitting of the original tool is really not good I think. Would it be possible to add me to the maintainers, please? --Dvorapa (talk) 13:50, 25 June 2018 (UTC)

Done. Thanks for taking it on. --Para (talk) 06:19, 27 June 2018 (UTC)
Thank you, I saw someone with adminship on Toolforge already uploaded my patch (I was a little bit persistent), but I will help with other issues too if they will arise. --Dvorapa (talk) 09:09, 19 August 2018 (UTC)