[01:13:10] <dschwen>	 hello! Toolforge bot operator who desperately wants to migrate from python2 to python3 here. Toolforge only has python3.5 but stuff like `import toolforge` requires at least 3.6. bd808 suggested I run my bot in a kubernetes container with python3.7, but how do I get stuff like the mwparserfromhell, pyexiv2, toolforge python modules in that
[01:13:11] <dschwen>	 container?
[01:14:29] <dschwen>	 s/pyexiv2/py3exiv2/g
[01:15:49] <wm-bb_>	 <bd808> dschwen: by using a python virtualenv to install whatever python modules your too needs. See https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Python
[01:16:18] <dschwen>	 ah, right! and sourcing i in my bot's start script
[01:16:29] <wm-bb_>	 <bd808> Yup!
[01:16:30] <dschwen>	 buuut, to build that env I need python3.7
[01:16:42] <dschwen>	 *runns off to read docs*
[01:17:26] <wm-bb_>	 <bd808> You do that by using ‘webservice python3.7 shell’ to get an interactive shell with py3.7
[01:18:07] <dschwen>	 ok, I was a bit confused because all teh docs just mention "webservice" which is not what I want to run
[01:18:11] <dschwen>	 thanks!
[01:19:26] <legoktm>	 dschwen: the toolforge Python library should only require Python 3.5 btw
[01:20:13] <wm-bb_>	 <bd808> Yeah, the docs are pretty incomplete today for using kubernetes for non-webservice things.
[01:22:10] <dschwen>	 legoktm, but it requires pymysql...
[01:22:21] <dschwen>	 which nowadays requires >=3.6
[01:22:39] <legoktm>	 https://github.com/legoktm/toolforge/blob/master/setup.py#L16
[01:22:48] <legoktm>	 it should install an older version on 3.5
[01:23:00] <legoktm>	 but you have to upgrade pip for that syntax to work
[01:23:13] <dschwen>	 what can I say, I created a venv, pip installed toolforge and importing fails
[01:23:21] <dschwen>	 ah
[01:23:28] <legoktm>	 try pip install -U pip; pip install toolforge;
[01:25:49] <dschwen>	 Ok, that certainly bumped my pi version from 9.x to 20.x, and it works now. Thanks!
[01:26:14] <legoktm>	 :D
[01:27:01] <dschwen>	 living onteh edge now (with this warning: "pip 21.0 will drop support for Python 3.5 in January 2021.") gulp!
[01:29:47] <dschwen>	 by the way, legoktm, thanks for the toolforge module, I've already been using it on a cloud vm project and it is nice not having to worry bout database servers moving around etc.
[01:30:08] <legoktm>	 You're welcome! That's exactly why I wrote it :D
[01:31:15] <dschwen>	 oh, boy, maybe I have to move to kubernetes after all. the exiv2 lib supplied with pyexiv2 requires a newer glibc:
[01:31:15] <dschwen>	 OSError: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /mnt/nfs/labstore-secondary-tools-project/gpsexif/gpsexif_bot/.venv/lib/python3.5/site-packages/pyexiv2/lib/libexiv2.so)
[01:31:35] <dschwen>	 or building exiv2 from source...
[07:32:17] <legoktm>	 !log library-upgrader deleting libup-diff01 experiment and upgrader-07 (puppet tests) instances
[07:32:20] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Library-upgrader/SAL
[07:34:29] <legoktm>	 !log library-upgrader creating libup-db01 instance
[07:34:31] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Library-upgrader/SAL
[08:12:13] <legoktm>	 !log library-upgrader importing mysql database on libup-db01
[08:12:17] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Library-upgrader/SAL
[08:12:28] <legoktm>	 (backed by cinder!)
[08:48:19] <legoktm>	 !log codesearch moved role::labs::lvm::srv from project puppet to codesearch06's puppet with the goal of moving to cinder
[08:48:22] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Codesearch/SAL
[08:52:44] <legoktm>	 !log codesearch creating codesearch7 instance (T279763)
[08:52:46] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Codesearch/SAL
[08:52:47] <stashbot>	 T279763: Move codesearch to cinder - https://phabricator.wikimedia.org/T279763
[08:57:07] <legoktm>	 aw crap, made it the wrong size
[08:57:40] <legoktm>	 !log deleting codesearch7, creating codesearch8 as the correct size (T279763)
[08:57:40] <stashbot>	 legoktm: Unknown project "deleting"
[08:57:48] <legoktm>	 !log codesearch deleting codesearch7, creating codesearch8 as the correct size (T279763)
[08:57:51] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Codesearch/SAL
[08:57:51] <stashbot>	 T279763: Move codesearch to cinder - https://phabricator.wikimedia.org/T279763
[09:05:23] <legoktm>	 hmm, I think my reformatting messed it up
[09:09:10] <legoktm>	 Apr 09 09:08:53 codesearch8 systemd[1]: srv.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-eb1f9c37\x2d1632\x2d4e29\x2da716\x2d0a65a913ac91.device. Stopping, too.
[09:10:12] <legoktm>	 systemctl daemon-reload fixed it
[11:05:44] <wm-bb>	 <JeanFred> Sooo, I gave this a try and could create a metric fine using echo "toolforge.integraality.run.$WIKI $elapsed_time_ms $(date +%s)" | nc -q0 cloudmetrics1002.eqiad.wmnet 2003 ;
[11:05:45] <wm-bb>	 <JeanFred> however I realize this is not correct statsd syntax is it ? To type it as a timer I should be using echo "toolforge.integraality.run.$WIKI:$elapsed_time_ms|ms − however that does not create any metric... Am I missing smth ? (re @wmtelegram_bot: <bd808> @JeanFred: you can use it, but also be aware that the service comes with no uptime or stability guarantees and may be completely removed at any time. There is an effort to remov
[15:11:44] <iosoio>	 You wikipedia guys are just great!:)
[15:16:23] <iosoio>	 I just discovered wikivoyage and it is great ! I think graphically it should be more prominent also while browsing the normal wikipedia.
[15:17:49] <Majavah>	 iosoio: this isn't the wikivoyage channel
[15:18:51] <Reedy>	 or the wikipedia one :P
[15:19:02] <iosoio>	 TY
[15:20:37] <bd808>	 iosoio: thank you for liking out projects though! :)
[15:21:48] <bd808>	 *our
[16:56:26] <Cyberpower678>	 I got a question for an SQL expert?
[16:57:15] <Cyberpower678>	 I'm adding a foreign key to a table, but the table is already populated and has a few rows that violate the constraint.  Anyway to have those rows automatically while the foreign key is being added?
[16:57:23] <Cyberpower678>	 *automatically delete
[17:34:27] <Cyberpower678>	 Anyone?
[17:36:01] <Reedy>	 It's probably easier to just remove those rows first
[17:36:21] <Reedy>	 also, this sounds very much a google-able problem
[18:02:28] <Cyberpower678>	 Reedy: you would think, but removing the row throws other problems.  I tried googling, but my either my google skills just suck, or there really is no answer, yet to what I'
[18:02:30] <Cyberpower678>	 m doing
[18:03:51] <Cyberpower678>	 removing the rows first, I meant to say.  One table doesn't seem to like it.
[18:06:33] <wm-bot>	 !log tools.lexeme-forms <lucaswerkmeister> deployed 18bb25abd0 (l10n updates)
[18:06:37] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL
[18:16:40] <wm-bot>	 !log tools.quickcategories <lucaswerkmeister> deployed 24f6e19113 (better workaround for T279585)
[18:16:44] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL