IRC logs of #tryton for Tuesday, 2023-05-02 #tryton log beginning Tue May 2 12:10:01 AM CEST 2023
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton05:22
-!- ChanServ changed mode/#tryton -> +o cedk 05:22
-!- springwurm(~springwur@2a01:76c0:302:ab00:9b5c:c469:518d:30df) has joined #tryton05:25
-!- tbruyere( has joined #tryton06:03
-!- acaubet(~Thunderbi@ has joined #tryton06:39
-!- mrichez(~Maxime@2a02:a03f:c2e8:f900:db7c:11fb:1fc6:3112) has joined #tryton07:38
-!- nicoe(~nicoe@2a02:578:852a:c00:18c2:1aff:fef9:2b7f) has joined #tryton08:41
-!- nicoe(~nicoe@2a02:2788:54:1ff:7e2a:31ff:fe5e:b25d) has joined #tryton12:05
-!- springwurm(~springwur@2a01:76c0:302:ab00:316:4534:6b8e:43bc) has joined #tryton12:07
-!- htgoebel( has joined #tryton12:17
htgoebelI'm trying to make trytond execute cron jobs.12:19
htgoebelEven if trytond is NOT running, trytond-cron fails with _TransactionLockError in lock_table.12:19
htgoebel(using sqlite backend)12:19
htgoebelfull traceback is at
htgoebelAny ideas?12:19
htgoebelsqlite is used since this is just a dev/test environment12:21
htgoebelIf there is some other way to trigger specific cronjobs, I'd happily use this (scheduling is not required)12:23
cedkLooks like we are missing a transaction error fix when locking cron table12:27
pokolihtgoebel: there is a run_once button on cron job to force its execution12:33
htgoebelcedk: anything I can contribute? example I can use as a base?12:34
-!- tbruyere1( has joined #tryton14:25
-!- tbruyere( has joined #tryton14:27
htgoebelcedk: many thanks for the quick fix. I'll test it tomorrow.15:59
-!- htgoebel( has left #tryton16:02
-!- rpit( has joined #tryton16:57
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton21:09
-!- ChanServ changed mode/#tryton -> +o cedk 21:09

Generated by 2.17.3 by Marius Gedminas - find it at!