| *** mbozem has quit IRC | 01:04 | |
| *** mbozem has joined #idempiere | 01:05 | |
| *** mbozem2 has joined #idempiere | 01:30 | |
| *** mbozem has quit IRC | 01:31 | |
| Not-bfd4 | [iDempiere4.1Daily] jenkins built #109 completed (success) http://ci.idempiere.org/job/iDempiere4.1Daily/109/ | 04:49 |
|---|---|---|
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3479 | 06:08 |
| Not-bfd4 | [IDEMPIERE] This should be added to core but must not be google implementation specific. There should be an interface to plugin different 2fa provider. Also, we can implement a default 2fa implementation in core that simply send a time limited, random tag/token to the login email account. | 06:08 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3479 | 06:08 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3406 | 06:20 |
| Not-bfd4 | [IDEMPIERE] I think it should be Order by QtyOnHand Desc instead. Filter out record with QtyOnHand = 0 could break use cases that need to update existing ASI with onhand = 0. | 06:20 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3406 | 06:20 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3456 | 06:29 |
| Not-bfd4 | [IDEMPIERE] I guess this can be make configurable with a new tenant level flag, for e.g ALLOW_REACTIVATE_CLOSE_PERIOD_ORDER. Should default to Y to maintain backward compatibility. | 06:29 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3456 | 06:29 |
| Not-bfd4 | [IDEMPIERE] hengsin created IDEMPIERE-3483 Issue to Project from Material Receipt => Error: Posts Unit Cost instead of Extended Cost | 06:45 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3483 | 06:45 |
| *** nmicoud has joined #idempiere | 06:45 | |
| Not-bfd4 | [iDempiere] hengsin pushed 1 commit to release-4.1 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/ | 06:49 |
| Not-bfd4 | [iDempiere] hengsin cc21c47 - IDEMPIERE-3483 Issue to Project from Material Receipt => Error: Posts Unit Cost instead of Extended Cost | 06:49 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3483 status set to "Resolved" -assignee set to "Chuck Boecking" -Fix Version set to "4.1" -resolution set to "Fixed" | 06:50 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3483 | 06:50 |
| Not-bfd4 | [IDEMPIERE] hengsin created IDEMPIERE-3484 ProjectIssue should create M_CostDetail record | 06:52 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3484 | 06:52 |
| Not-bfd4 | [iDempiere] hengsin pushed 1 commit to release-4.1 [+0/-0/±2] https://bitbucket.org/idempiere/idempiere/commits/ | 06:57 |
| Not-bfd4 | [iDempiere] hengsin 45aad54 - IDEMPIERE-3484 ProjectIssue should create M_CostDetail record | 06:57 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3484 status set to "Resolved" -assignee set to "Chuck Boecking" -Fix Version set to "4.1" -resolution set to "Fixed" | 06:57 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3484 | 06:57 |
| Not-bfd4 | [IDEMPIERE] nmicoud updated IDEMPIERE-3478 status set to "Peer Review Queue" | 06:57 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3478 | 06:57 |
| Not-bfd4 | [IDEMPIERE] nmicoud updated IDEMPIERE-3478 assignee set to "Carlos Ruiz" | 06:57 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3478 | 06:58 |
| Not-bfd4 | [IDEMPIERE] nmicoud updated IDEMPIERE-3478 labels set to "+Patch" | 06:58 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3478 | 06:58 |
| Not-bfd4 | [iDempiere] hengsin pushed 1 commit to release-4.1 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/ | 07:01 |
| Not-bfd4 | [iDempiere] hengsin a8634ef - IDEMPIERE-3361 Cost details inherit amt/qty from wrong history cost element | 07:01 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3361 status set to "Resolved" -assignee set to "Norbert Bede" -Fix Version set to "4.1" -resolution set to "Fixed" | 07:03 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3361 | 07:03 |
| *** a42niem has joined #idempiere | 07:06 | |
| Not-bfd4 | [iDempiere4.1] jenkins built #185 completed (success) http://ci.idempiere.org/job/iDempiere4.1/185/ | 07:15 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3061 status set to "Resolved" -assignee set to "Daniel Haag" -resolution set to "Won't Fix" | 07:27 |
| Not-bfd4 | [IDEMPIERE] The patch is outdated. Please reopen with a new patch and test case if the problem is still there in current 4.1 code. | 07:27 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3061 | 07:27 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-2953 priority set to "Major" | 07:28 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2953 | 07:28 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-2953 | 07:29 |
| Not-bfd4 | [IDEMPIERE] This probably wouldn't be fixed in short to mid term. Workaround is to use Average PO Costing with Batch Level Costing. | 07:29 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2953 | 07:29 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-2603 status set to "Resolved" -resolution set to "Cannot Reproduce" | 07:47 |
| Not-bfd4 | [IDEMPIERE] Not reproduceable with current 4.1 code. Please reopen with test case if you can reproduce it. | 07:47 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2603 | 07:47 |
| *** CarlosRuiz has joined #idempiere | 07:56 | |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-2659 status set to "Closed" -resolution set to "Fixed" | 08:07 |
| Not-bfd4 | [IDEMPIERE] This should have been fixed in current 4.1 code. Please reopen if that's not the case. | 08:07 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2659 | 08:07 |
| Not-bfd4 | [IDEMPIERE] hengsin created IDEMPIERE-3485 Report/Process: Unique constraint exception after save parameter | 08:17 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3485 | 08:17 |
| *** a42niem has quit IRC | 08:27 | |
| Not-bfd4 | [iDempiere] hengsin pushed 1 commit to release-4.1 [+0/-0/±2] https://bitbucket.org/idempiere/idempiere/commits/ | 08:35 |
| Not-bfd4 | [iDempiere] hengsin 62c83bf - IDEMPIERE-3485 Report/Process: Unique constraint exception after save parameter | 08:35 |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3485 status set to "Resolved" -Fix Version set to "4.1" -resolution set to "Fixed" | 08:36 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3485 | 08:36 |
| Not-bfd4 | [iDempiere4.1] jenkins built #186 completed (success) http://ci.idempiere.org/job/iDempiere4.1/186/ | 08:42 |
| *** marcofontell has joined #idempiere | 12:03 | |
| Not-bfd4 | [IDEMPIERE] hieplq updated IDEMPIERE-3480 | 12:30 |
| Not-bfd4 | [IDEMPIERE] 2Pack also got issue with huge record. i try to use 2Pack for about 500.000 product price it take long time (about 7h) and end with exception transaction timeout i think overload stay at get ID of table and save change log | 12:30 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3480 | 12:30 |
| *** marcofontell has quit IRC | 12:32 | |
| *** victorgomez has joined #idempiere | 12:42 | |
| Not-bfd4 | [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-3480 | 12:43 |
| Not-bfd4 | [IDEMPIERE] [~hieplq], 2pack is designed to do all the work within a single transaction, so loading 500.000 records with 2pack can lead to a big long trx - I think is not the intention of 2pack to load such big data. About CSV import - it can work within a single transaction or transaction per line depending on the configuration of the CSV file - for better results in a big load case like you try the transaction must | 12:43 |
| Not-bfd4 | be per line. I think CSV import is slow and memory-hungry because it was designed to emulate a user typing in the window, so, it uses all the UI-related structures. That has a big advantage and is that callouts are executed as if the user is typing in the window, but cannot give the same speed and memory than a direct-model importer (not using the UI). We have annotated that as a "known-issue" for CSV importer and | 12:43 |
| Not-bfd4 | recommendation is to split the file in manageable sizes. Or, for big data, use the old importers when available, in the case of product price import there is an old non-UI importer that can be used. But, of course, any improvement in memory/speed for the CSV importer that doesn't break the UI-emulation functionality is welcome. | 12:43 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3480 | 12:43 |
| victorgomez | hi all | 12:51 |
| victorgomez | have anybody here faced a GenerateDocumentNoTimeOut problem when running InvoiceGen process in a large database (postgresql) ? | 12:52 |
| victorgomez | explaining better, when a user is generating invoices other users inputing manual invoices get locket with GenerateDocumentNoTimeOut | 12:53 |
| victorgomez | as i understand is in due of a ad_sequence lock | 12:53 |
| *** marcofontell has joined #idempiere | 13:07 | |
| CarlosRuiz | yes victorgomez - the InvoiceGen run in a single transaction | 13:16 |
| CarlosRuiz | and in some big load environments can cause that | 13:16 |
| CarlosRuiz | do you know how to open a ticket on JIRA? | 13:17 |
| victorgomez | thank you for your feedback CarlosRuiz... | 13:18 |
| victorgomez | yes, i know... should i do it? | 13:18 |
| victorgomez | just two more related itens, my ad_changelog table have 39.436.973 records... it's a good pratice clear old records there? and also i was looking into pool.properties file (PostgreSQL folder in server home) if there's something to change there that can avoid the timeout, but i think that the answer is "no" | 13:22 |
| *** marcofontell has quit IRC | 13:26 | |
| CarlosRuiz | yes - that can be an improvement - to process a transaction per invoice | 13:35 |
| CarlosRuiz | for pool.properties you can check the options that c3p0 library provides - but I think it's not related to timeouts | 13:35 |
| CarlosRuiz | about cleaning ad_changelog - yes - you can clear it if you don't need it - is audit information - there is a Housekeeping feature where you can save it to XML - or move records to a historic table - and also schedule it to do it periodically | 13:36 |
| victorgomez | oh, alright.... i'll do that... | 13:50 |
| victorgomez | and also check the housekeeping feature!! thank you!! | 13:50 |
| Not-bfd4 | [iDempiere] hengsin pushed 1 commit to release-4.1 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/ | 13:51 |
| Not-bfd4 | [iDempiere] hengsin 5aa871f - IDEMPIERE-3485 Report/Process: Unique constraint exception after save parameter | 13:51 |
| Not-bfd4 | [IDEMPIERE] hieplq updated IDEMPIERE-3480 | 14:20 |
| Not-bfd4 | [IDEMPIERE] thanks [~carlosruiz_globalqss] for comment. finally i import by sql with id = current + row_number() after that update seq, very fast, about 3 minute. about long time transaction, i read discuss here IDEMPIERE-644 and agree with it. about tab csv import. it can slow but shouldn't take a lot of memory not yet take time to discover, but i guess by it keep one install of window to import data, so end up it | 14:20 |
| Not-bfd4 | like you load 500.000 record on this window. so it should refresh window instance after like 100 master record (that should on parameter). | 14:20 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3480 | 14:20 |
| Not-bfd4 | [IDEMPIERE] hieplq created IDEMPIERE-3486 info business partner hard code to set isCustomer, isVendor, so break "Value Preference " and avoid customize | 14:22 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3486 | 14:22 |
| Not-bfd4 | [iDempiere4.1] jenkins built #187 completed (failure) http://ci.idempiere.org/job/iDempiere4.1/187/ | 14:25 |
| Not-bfd4 | [IDEMPIERE] hieplq updated IDEMPIERE-3486 labels set to "+Patch" | 14:29 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3486 | 14:29 |
| Not-bfd4 | [IDEMPIERE] hieplq updated IDEMPIERE-3486 Attachment set to "IDEMPIERE-3486.patch" | 14:30 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3486 | 14:30 |
| Not-bfd4 | [IDEMPIERE] hieplq updated IDEMPIERE-3486 status set to "Peer Review Queue" | 14:30 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3486 | 14:30 |
| *** victorgomez has quit IRC | 14:40 | |
| Not-bfd4 | [IDEMPIERE] hieplq created IDEMPIERE-3487 price list version on product info show ever PLV from inactive price list | 14:42 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3487 | 14:42 |
| Not-bfd4 | [IDEMPIERE] hieplq updated IDEMPIERE-3487 | 14:47 |
| Not-bfd4 | [IDEMPIERE] PLV also should fill out by price list when open on window like sales order, purchase,... | 14:47 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3487 | 14:47 |
| *** nmicoud has quit IRC | 15:21 | |
| *** Slug_ has joined #idempiere | 15:26 | |
| Not-bfd4 | [IDEMPIERE] hengsin updated IDEMPIERE-3413 | 16:29 |
| Not-bfd4 | [IDEMPIERE] JSON is supported by both PostgreSQL and Oracle so that could be a viable alternative here | 16:29 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3413 | 16:29 |
| *** mbozem2 has quit IRC | 18:09 | |
| *** CarlosRuiz has left #idempiere | 18:41 | |
| Not-bfd4 | [IDEMPIERE] norbert.bede updated IDEMPIERE-3413 | 21:34 |
| Not-bfd4 | [IDEMPIERE] +1 for json solution. generally json fieldtype is really missing in idempiere. (another ticket) | 21:34 |
| Not-bfd4 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3413 | 21:34 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!