I'm the rare one who codes in Tcl.
- User Since
- Oct 17 2014, 11:21 AM (450 w, 1 d)
- IRC Nick
- LDAP User
- MediaWiki User
- Giftpflanze [ Global Accounts ]
Tue, May 9
I am sorry for the slow response. The tool is not running any scheduled jobs on the grid atm and I have no plans to migrate to custom images for the time being. But if I were, from the linked documentation I wouldn't have more than a vague idea how to build an image with a few packages added.
Oct 17 2022
It is the Factor VM (~tools.giftbot-factor/factor/factor; https://factorcode.org). When I try to run it with the image (or any other image as far as I remember) and use SSL, the following error message appears:
Oct 13 2022
Today over the mailinglist is the first time I learned about this type of ticket.
Aug 23 2022
Thank you for you work! I have created a new VM, transfered the data and deleted the volume and the old VM.
Aug 20 2022
I'd like to rebuild the VM. Could you please give me the home directories of gifti and taxonbot?
Aug 12 2022
Retrying failed jobs is not always acceptable. There should be an option to try jobs only once.
Jul 26 2022
Jul 25 2022
I have now realized that I have the same problem with the bot GiftBot on dewiki. Several scripts are stuck in endless loops because they cannot get valid tokens.
Jul 24 2022
The bots authenticate via OAuth owner-only consumers. The source code is in ~taxonbot on the instance taxonbot.dwl on WMCS. It can also be found here: https://github.com/gifti258/taxonbot
May 20 2022
May 14 2022
I have flushed the jobs and rescheduled most of them on the 7th minute, like I did for sge. I hope that helps with the load (if it is that).
May 13 2022
Mar 30 2022
I recompiled vim on buster, this shouldn't be necessary anymore.
I'm looking forward to the custom containers, and in the meantime I compiled tdb/fdm.
Mar 29 2022
Apparently k8s tries to run the command a second time in case of failure. Is that intentional?
Mar 28 2022
Could this be because I already have 3 deployments (1 k8s webservice and 2 continuous jobs) and adding another continuous job would exceed my quota?
Mar 26 2022
Jan 17 2022
Can I get any progress on this?
Dec 19 2021
I want to to process daily emails that contain data for a commons data table.
Dec 14 2021
Nov 3 2021
Jun 12 2021
If you want, you can now lower CPU quota to 65 cores and RAM quota to 146.048 MB.
May 26 2021
I confirm. It also includes the new flavor.
May 20 2021
Apr 7 2021
Um, no. We can't move forward with transition yet. Afais, instance resizing isn't enabled yet, but that's a prerequisite. After that, we'll probably need a few days, depending on my and Doc Taxon's availability.
Mar 24 2021
Mar 17 2021
Oct 26 2020
Should be fixed now.
Dec 24 2019
Dec 20 2019
Dec 6 2019
Oct 3 2019
Sep 30 2019
Jan 31 2019
Jan 25 2019
I wonder why it worked with the new tclsh binary and tcl libraries on the old tcl container then.
Ok, so now my kubernetes webservice of type tcl doesn't work anymore, it is missing libmariadbclient.so.18.
Jan 23 2019
I thought I needed the packages as runtime on the exec nodes. I don't know if anything has changed on them but I do no longer seem to need this as it just works fine now.
As it turns out, I found an old workaround that does away with the dependency of bc in the build process.
Jan 13 2019
Nov 30 2018
Nov 27 2018
May 15 2018
The repo apparently was archived in gerrit directly. This is now undone. There also was no +2 right for me, which is now added. A jenkins integration would be nice to have but in the meantime I can make do with submitting directly.
May 14 2018
Despite https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL and IRC suggesting otherwise, the repo is still archived and gerrit still refuses patches.
May 12 2018
Could you please un-archive labs/tools/giftbot?
May 2 2018
Jan 22 2018
You're right, it seems that we don't need so much RAM at the moment. At least it was necessary in the past or otherwise the instance would be really slow. I think we could first try with an xlarge instance.
Jan 20 2018
Aug 8 2017
I went through my table creation statements and added engine statements. I dropped four tables that I want to recreate and changed the engine of the remaining to InnoDB. Thank you for your prompt reaction!
Mar 6 2017
< yuvipanda> !log tools set complex_values slots=300,release=trusty for tools-exec-gift-trusty-01.tools.eqiad.wmflabs
This seems to have done the trick, thank you!
@chasemp The old instance can be cleaned up now.
Feb 26 2017
Killing the Precise instance (and defaulting to Trusty) shouldn't pose a problem. I switched my code to Trusty (I didn't even know anymore that I had to hardcode that) and I will test it with the next regular run starting on the 1st of March. (Also, I'm kinda swamped with school stuff but I'm glad to have found a minute for this.)
Feb 17 2017
Feb 15 2017
< annika> chasemp: […] I guess you mean: You will provide a trusty exec node with an appropriate queue? And I will just use that instead of the current one?
< chasemp> annika: basically, a second trusty node in the same queue for you to migrate to
< annika> that would be fine
Jan 25 2017
So, we deleted the old instace before creating the new one anyway because we wanted to keep the name. You can now readjust the quota.
Jan 19 2017
Jan 18 2017
Considering my earlier comment (bigram instance), the needed numbers would be 1+8=9 cores and 2+36=38GB. But otherwise you're right. And I actually planned to do the transition without additional temporary resources. But it surely would give us more security.
I'm not aware of any script errors. Maybe there are db queries or other things that cause it to hang.
Dec 19 2016
We need more RAM for data processing. We are not aware of other possibilities. Afais, "bigram" has even more RAM, so we'd like to have enough room for 1 small and 1 bigram instance.
Dec 5 2016
Aug 28 2016
Aug 6 2016
Seems to work again.
Jul 26 2016
Jul 5 2016