[00:04:15] <Jayprakash12345>	 !log tools.indic-wscontest Sort contests by their descending order of creation date (T252608)
[00:04:17] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.indic-wscontest/SAL
[00:04:17] <stashbot>	 T252608: indic-wscontest: Sort contests by their descending order of creation date - https://phabricator.wikimedia.org/T252608
[13:56:29] <isaacj>	 q: if i'm having trouble getting a python library installed on toolforge (https://github.com/facebookresearch/fastText -- my best guess is that the issue likely has to do with C++ compilers :/ ), what's the best way to get support with that (IRC, phab task?, email?, etc.)? the library actually used to be installed on my virtualenv but in attempting to migrate to kubernetes + python3.7, it's no longer functioning
[13:59:32] <arturo>	 yes a phab task might be in the right thing to do
[14:00:16] <isaacj>	 :thumbs up: thanks! tag cloud-services-team or is there another way to route it?
[15:24:35] <bd808>	 isaacj: tags with #toolforge for sure. we should see it pop up there and add other tags as needed
[15:37:47] <isaacj>	 bd808: thanks!
[18:10:21] <bstorm_>	 !log tools set "profile::toolforge::k8s::typha_enabled: true" in tools project for calico upgrade T250863
[18:10:25] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[18:10:25] <stashbot>	 T250863: Upgrade calico to a more recent version (current is 3.14.0) - https://phabricator.wikimedia.org/T250863
[18:14:15] <bstorm_>	 !log tools upgrading calico to 3.14.0 with typha enabled in Toolforge K8s T250863 
[18:14:18] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[22:05:24] <wm-bot>	 !log tools.lexeme-forms <lucaswerkmeister> deployed a2deb7908c (update past participle item ID after merge)
[22:05:26] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL
[22:26:21] <bd808>	 isaacj: I put a work around for you in the bug you reported. the real problem was sneakily hidden in by the not very portable code in that library
[22:26:58] <isaacj>	 just seeing this -- this is fantastic thank you! i will try to port over to kubernetes now and let you know if it's successful on the task