IRC logs of #tryton for Thursday, 2019-10-10 #tryton log beginning Thu 10 Oct 2019 12:00:01 AM CEST
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton22:42
-!- yangoon( has joined #tryton02:27
-!- nminix__( has joined #tryton02:49
-!- thaneor1( has joined #tryton03:38
-!- semarie(~semarie@unaffiliated/semarie) has joined #tryton04:37
-!- odicha(~odicha@ has joined #tryton05:16
-!- hedererjs(~hedererjs@ has joined #tryton05:38
-!- nminix__( has left #tryton05:50
-!- mrichez( has joined #tryton06:22
-!- semarie(~semarie@unaffiliated/semarie) has joined #tryton06:25
-!- springwurm(~Springwur@ has joined #tryton06:54
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton07:08
-!- thaneor( has joined #tryton07:26
mrichezhi, after a pull update on trytond test installation, i launch command trytond-admin -c ... -d .... --all -vvv ... it seems blocked... here's the last query displayed:07:38
mrichezhow to know which module is faulty for this blocked query ?07:39
mrichezafter ctrl-break... i retry same command with -u country ... the problems seems there07:40
semariemrichez: which trytond version ? what is the process state for trytond-admin or postgresql processes ? busy, locked, idle ?07:45
mrichezsemarie: trytond tip (5.3); don't know the state (100% cpu used) running07:48
mrichezinfinite loop or query ?07:49
semariehere, I am fine with effd37625813 (tryton-env)07:59
semariebut we might not using the same modules07:59
mrichezsemarie: indeed, will retry with fresh install (but got same problem on 2 different installations)08:00
-!- nicoe(~nicoe@2a02:2788:54:5a3:7e2a:31ff:fe5e:b25d) has joined #tryton08:16
mrichezhi, following previous discussion, i'm retrying on a fresh install 5.3 dev,... activating country and currency modules... executing first script to import countries, got this error:
-!- Timitos(~kpreisler@2001:a61:5a4:b101:762b:62ff:fe84:ed7e) has joined #tryton09:10
pokolimrichez: You should report this as a bug09:31
mrichezpokoli: ok09:31
pokolimrichez: it will be great to know which pycountry version you have installed09:35
mrichezpokoli: pycountry 19.8.1809:36
pokolimrichez: have you tested with previous pycountry version?09:36
mrichezpokoli: no09:37
pokolimrichez: as it seems that the problem is data related (but probably the script should not fail in such case), using the previous version may fix the issue09:37
mrichezsemarie: and concerning my previous problem with query blocked, it is solved after a "Synchronize Translations"09:38
mrichezpokoli: will retry with a previous version09:38
pokoliACTION checking with an older version09:39
pokolimrichez: no error with pycountry==18.5.2609:39
mrichezpokoli: ok, will check with 19.7.1509:40
mrichezpokoli: still not working with 19.7.1509:44
mrichezpokoli: another error with 18.12.8 :
mrichezpokoli: same error with 18.5.26 :   but maybe because i've already executed script ???09:47
pokolimrichez: this context error is strang and it should no happen09:48
pokolimrichez: I tested creating a new database with only country module and executing the script09:48
mrichezpokoli: will scratch my db and retry09:57
mrichezpokoli: working on fresh database with 18.5.2610:01
mrichezpokoli: working on fresh database with 18.12.810:07
-!- udono( has joined #tryton10:11
mrichezpokoli: error on fresh database with 19.7.15 :
cedkit should be fixed with
cedkpycountry has a strange management of parent_code and new version has more sub-subdivisions10:15
mrichezcedk: ok thanks :-)10:19
cedkindeed what happens is that pycountry append in parent_code always the country code but on the second level of the tree the country code is added twice10:24
-!- hedererjs(~hedererjs@ has joined #tryton11:22
mrichezcedk: working with patch with pycountry 19.7.1511:24
-!- mrichez( has joined #tryton11:45
-!- mariomop(~quassel@ has joined #tryton11:51
-!- springwurm(~Springwur@ has joined #tryton12:19
-!- nicoe( has joined #tryton12:54
-!- sebste( has joined #tryton14:54
-!- smorillo(250f660a@gateway/web/cgi-irc/ has joined #tryton14:58
sebstecedk: Good evening! You there?15:15
pokolisebste: good evening, I'm hereee :)15:21
sebstepokoli: Oh, hi! That's also awesome! :-D15:21
sebsteNot sure if you followed the discussion last time... cedk suggested to rename the _temp_month column ....15:23
sebstein account_invoice_payment_term_line_delta15:23
pokolisebste: yes, I've read it and I remember15:23
sebsteappearently trytond-admin did not finish the update15:23
sebsteSo I managed to do that.15:24
sebsteWhen I rerun trytond-admin -c /etc/tryton/trytond.conf -d /home/tryton_sys/tryton5_lcc_db --all I run into another problem (maybe the initial one15:24
sebsteIt fails with: sqlite3.OperationalError: index account_invoice_payment_term_line_delta__history_id_index already exists15:25
sebsteAfter that, the same _temp_mont column is bach in the schema15:25
sebsteany pointers on how to chase such a failing update down? Problem is I don't even understand how trytond-admin does these db updates15:27
sebsteor where to start looking15:27
pokolimmm it seems that it fails when creating an index on hte __history table15:27
pokolithe __history table is there to save all the modifications done to the payment_term_line_delta table15:28
pokolisebste: probably manually removing the index (and the temp column) should fix it15:28
sebstepokoli: ok? so how would i remove the index?15:30
sebstepokoli: sorry for bothering you with probably basic questions.15:31
sebstepokoli: so basically :DROP INDEX account_invoice_payment_term_line_delta__history_id_index; ?15:34
pokolipokoli: drop the index, drop the column and execute tryton-admin another time15:35
pokolisebste: tryton-admin checks the database structure and creates the missing fields, executes migrations and so one15:35
sebstepokoli: thanks. That worked!!! You are awesome!15:39
pokolisebste: indeed you did all the work which was finding the root cause of the problem15:39
-!- rpit( has joined #tryton15:40
sebstepokoli: yea, but I dod not know what I lokked at :-D15:40
sebsteBy the way... can I ask another question? What would be the proper way to switch from minimal chart of accounts to another one like say SKR03?15:42
pokolisebste: indeed your case is very strange15:42
pokolisebste: you can install the new module and then create the new chart of accounts15:42
pokolisebste: you will get a warning about a duplicate chat but you can ingnore it15:43
pokolisebste: and then it's a mather of removing the miniaml account data15:43
pokolisebste: did you have any account_moves on the system?15:43
sebsteyes, for testing, generated by invoices, i guess, but nothing relevant15:44
-!- smorillo(250f660a@gateway/web/cgi-irc/ has joined #tryton15:45
pokolisebste: if you only have testing data probably it's worth to remove the database and start with a fresh one15:45
pokolisebste: in this case you can also switch from sqlite to postgresql15:46
sebstepokoli: yes, I was thinking about that... thing is I already invested in a lot of configuration / translation which I would have to redo. If there is a way around that I would not be angy.15:47
sebsteWas also thinking of migrating the existing db to postgresql. Though I like the lightness of sqlite and performance will not be an issue.15:49
pokolisebste: we have  a script to migrate from sqlite to postgresql:
pokolisebste: but i've never used it15:56
pokolisebste: if you want to keep the existing data is a mather of removing the data from the invoices, accounting, and all the chart configuration15:56
pokolisebste: there are some models that should be deleted15:56
sebstepokoli: Oh, that's cool! I'll have a look, thanks15:57
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton21:21

Generated by 2.17.3 by Marius Gedminas - find it at!