#idempiere IRC log for Wednesday, 2016-05-11

« Tuesday, 2016-05-10 Index Thursday, 2016-05-12 »
*** CarlosRuiz has left #idempiere01:41
*** a42niem has joined #idempiere04:39
*** HideakiHagiwara has joined #idempiere04:51
*** nmicoud has joined #idempiere06:46
*** KermitTheFragger has joined #idempiere06:46
*** a42niem has quit IRC07:30
*** a42niem_ has joined #idempiere08:18
*** aguerra has joined #idempiere12:39
aguerraGood morning for all!!!!!!!!12:39
*** HideakiHagiwara has joined #idempiere12:59
*** HideakiHagiwara has quit IRC13:07
*** norbertbede has joined #idempiere13:14
norbertbedehi all13:14
*** Deepak_ has joined #idempiere13:19
*** norbertbede has quit IRC13:47
*** hieplq has joined #idempiere14:00
*** norbertbede has joined #idempiere14:01
*** mand1nga has joined #idempiere14:05
norbertbedehi @Deepak_14:07
norbertbedewe have an issue with auth. token caching14:07
norbertbedeayt ?14:07
*** CarlosRuiz has joined #idempiere14:37
*** druiz has joined #idempiere14:45
Deepak_Sorry Norbertede, i got a pone call14:45
Deepak_*phone14:46
Deepak_Can you describe what is issue?14:46
norbertbedehi14:47
norbertbedei have customer at office. come back later14:48
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-302315:02
Not-aaf4[IDEMPIERE] Hi [~hieplq], actually the sessions have a reference to the node where they reside via the ServerName column, that's how in LoggedSessionListener.DestroyAllSession are cleared. I see also there is a call to DestroyAllSession in ContextDestroyed, and just tested and is correctly ran when you stop the server from the OSGi console, but maybe is not happening when you stop it using kill as in the init.d15:02
Not-aaf4script. So, seems like our problem is on the init.d/idempiere script - instead of calling kill to stop the server we need first to try to stop the OSGi server using properly the console. WDYT? Regards, Carlos Ruiz15:02
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-302315:02
*** hieplq has quit IRC15:08
Not-aaf4[iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-3.1 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/15:13
Not-aaf4[iDempiere] hie...@hasuvimex.vn ac341a3 - IDEMPIERE-3048:Wrong type when get AdWindow instance15:13
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-3048 status set to "Resolved" -assignee set to "hieplq" -resolution set to "Fixed"15:13
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:13
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2676 status set to "Reopened" -resolution set to "None"15:24
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-267615:24
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2676 summary set to "Incorrect context variables - onNavigate Callout"15:24
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-267615:24
*** a42niem_ has quit IRC15:32
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-267615:34
Not-aaf4[IDEMPIERE] You're right [~hieplq], wondering how can we implement the ability to run a read-only Callout when the document is completed. I mean, in principle it sounds ok to avoid running Callouts on completed documents as they could try to change values. But this can be useful for example to load context variables when navigating to a record. Running read-only callouts (callouts that don't change values, but maybe15:34
Not-aaf4just load context variables) could be safe on completed documents, would be a way to define that? I'm not sure if that can be done with window event validators. Now, wondering also, at this moment the callout is run on AlwaysUpdatable fields even on completed documents, so, you can setup a Callout on an AlwaysUpdatable field that change values for completed documents. So, would be ok to run the callout for key15:34
Not-aaf4(onNavigate callout) at least on completed docs?15:34
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-267615:34
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-267615:36
Not-aaf4[IDEMPIERE] This would be the patch to implement the latest suggestion (run always callouts on key records): {code} diff -r ac341a3f58ca org.adempiere.base/src/org/compiere/model/GridTab.java --- a/org.adempiere.base/src/org/compiere/model/GridTab.java Thu Mar 03 02:41:01 2016 +0700 +++ b/org.adempiere.base/src/org/compiere/model/GridTab.java Wed May 11 08:35:58 2016 -0700 @@ -2826,7 +2826,7 @@ public String15:36
Not-aaf4processCallout (GridField field) { // - if (isProcessed() && !field.isAlwaysUpdateable()) // only active records + if (isProcessed() && !field.isAlwaysUpdateable() && !field.isKey()) // only active records return ""; // "DocProcessed"; Object value = field.getValue(); {code}15:36
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-267615:36
*** KermitTheFragger has quit IRC15:40
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-3048 status set to "Reopened" -resolution set to "None"15:45
Not-aaf4[IDEMPIERE] this patch will open other issue: "NPE when open accout dialog from any account tab" so, please also commit my new patch15:45
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:45
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-3048 Attachment set to "IDEMPIERE-3048_1.patch"15:45
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:45
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-3048 status set to "Peer Review Queue"15:45
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:45
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-304815:47
Not-aaf4[IDEMPIERE] Sorry [~hieplq], how to reproduce "NPE when open accout dialog from any account tab"15:47
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:47
Not-aaf4[iDempiere3.1] jenkins built #85 completed (success) http://ci.idempiere.org/job/iDempiere3.1/85/15:54
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-304815:55
Not-aaf4[IDEMPIERE] if i correct, you just open any dialog to set up accounting combine. example:Business Partner/Customer Accounting field "Customer Receivables"15:55
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:55
*** nmicoud has quit IRC15:58
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-304815:58
Not-aaf4[IDEMPIERE] No, I tried that and is working fine. I see the first part of your patch can't be merged, the ADTabPanel doesn't have that code now. For the WindowValidatorManager part, you cannot add events on non-dictionary windows, but still would be worthy as safety against NPE. Is it ok to integrate just second part? Or first is needed somewhere else?15:58
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304815:58
*** norbertbede has quit IRC16:02
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-304816:04
Not-aaf4[IDEMPIERE] in my repository i have both. but maybe something out date when i merger with core. let me check on a clear idempiere code. i will give you correct patch. now please go with other issue.16:04
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304816:04
*** a42niem has joined #idempiere16:12
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-302316:32
Not-aaf4[IDEMPIERE] hi [~carlosruiz_globalqss], not only case use kill, it's cover case power suddenly turn off, or something make server crash or wrong network. I see "ServerName column" but maybe i just think over. in test environment sometime you have to run muilti instance of idempiere on same PC16:32
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-302316:33
*** druiz has quit IRC16:45
Not-aaf4[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-302316:58
Not-aaf4[IDEMPIERE] Yep - ServerName has more information, like port and IP I think. So, if I understood in your approach other servers can mark sessions as finished when one server fails - is there one leading that task? Or all of them do it? Can it be done as a scheduled process specific to an IP address? That checks (ping) the server in some way to see if is alive?16:59
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-302316:59
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-302317:07
Not-aaf4[IDEMPIERE] yes. it done at step 3 3. server will update active time of record each 5 minute (this value can configuration) i create a new view to fill out session of server have active time > 5 minute (this value can configuration) other server not need ping to check status of one server.17:07
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-302317:07
Not-aaf4[IDEMPIERE] hieplq updated IDEMPIERE-304817:20
Not-aaf4[IDEMPIERE] i just re-checked it. [^IDEMPIERE-3048_1.patch] when apply to core, just apply for class WindowValidatorManager code in ADTabpanel is my customize code to implement IDEMPIERE-2676 now don't have any case to procedure issue but it's a implicit issue.17:20
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-304817:20
*** CarlosRuiz has quit IRC17:29
*** Deepak_ has quit IRC17:42
*** CarlosRuiz has joined #idempiere18:09
*** norbertbede has joined #idempiere18:40
*** CarlosRuiz has quit IRC19:48
*** a42niem has quit IRC19:59
Not-aaf4[IDEMPIERE] jaimegarciaduque@gmail.com created IDEMPIERE-3095 Bug when you tried to define a second accont schem20:03
Not-aaf4[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-309520:03
*** aguerra has quit IRC21:32
*** norbertbede has quit IRC21:51
*** mand1nga has quit IRC21:56
« Tuesday, 2016-05-10 Index Thursday, 2016-05-12 »

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!