Activity for Hieu Nguyen
-
Hieu Nguyen created ticket #2778
pyosaf: add more attrDefaultValue into get_class_description()
-
pyosaf: refactor IMM utils
-
commit 842cf55fc3d443998a30181ae944720201f98cec Author: Hieu Nguyen hieu.t.nguyen@dektech.com.au Date: Wed Nov 22 11:40:20 2017 +0700 pyosaf: refactor IMM utils [#2683] + improve OI utils use a separate instance OM agent + refactor OM utils with Ccb inheritace OmAgent, rename some classes...
-
pyosaf: refactor IMM utils [#2683]
-
pyosaf: refactor IMM utils [#2683]
-
pyosaf: refactor IMM utils [#2683]
-
pyosaf: refactor IMM utils
-
pyosaf: refactor IMM utils [#2683]
-
pyosaf: refactor IMM utils
-
pyosaf: improve OI utils use a separate instance OM agent
-
pyosaf: refactor IMM samples to use new pyosaf utils version 1.0.0
-
pyosaf: High level python interfaces for IMM [#2602]
-
pyosaf: High level python interfaces for IMM [#2602]
-
pyosaf: retry SAF initialize() function with original version [#2524]
-
pyosaf: decorate function does not handle version struct in initialize functions [#2524]
-
pyosaf: Raise ValueError instead NoneType Exception [#1410]
-
pyosaf: Invalid exception used in ImmObject (object.py)
-
pyosaf: Invalid exception used in ImmObject (object.py)
-
pyosaf: IMM OM module initialized with ERR_BAD_HANDLE
-
I have been discuss with Zoran and set 'wontfix' to this ticket: Hi Hieu, Just talked with a girl who was involved in raising this ticket, and she said that it's ok. So, you have ack from me on this. Thanks, Zoran
-
Another ticket #2602 related to support handle ERR_BAD_HANDLE case. It's propose support more error codes should be handled as well, NOT only ERR_BAD_HANDLE. It's not "This should be done automatically in the retry loop". Please contact who handle this ticket get more detail. https://sourceforge.net/p/opensaf/tickets/2602/
-
Solution: + Backup current version in ERR_TRY_AGAIN case, and re-initialize with current version + Use initialize_decorate() function apply for all services in pyosaf utils
-
pyosaf: decorate function does not handle version struct in initialize functions
-
pyosaf: decorate function does not handle version struct in initialize functions [#2524]
-
In progress
-
pyosaf: decorate function does not handle version struct in initialize functions
-
pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
-
commit dfb0d550adb44e148001beb5237559b3e472fd9c Author: Hieu Nguyen hieu.t.nguyen@dektech.com.au Date: Wed Oct 4 11:12:43 2017 +0700 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules [#2533] + Remove a preceding underscore character of the initialize method in immom + Does not automatically called initialize() when the module is implemented
-
Hi, According to Johan's idea: "This should be done automatically in the retry loop". I want make clearly about this: In BAD_HANDLE case difference with TRY_AGAIN case + TRY_AGAIN is a simple case that's mean try to call current function agian. + BAD_HANDLE have many complex cases. Example for a CCB: Init OM handle => OK Init Admin Owner handle => OK Init CCB handle => OK Create a object => OK Modify this object => OK Apply CCB => BAD_HANDLE If we handle BAD_HANDLE case use Johan's idea, we need...
-
I set this ticket to "wontfix". If you have any comments, let me know ?
-
pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
-
Hi, According to Johan's idea: "This should be done automatically in the retry loop". I want make clearly about this: In BAD_HANDLE case difference with TRY_AGAIN case + TRY_AGAIN is a simple case that's mean try to call current function agian. + BAD_HANDLE have many complex cases. Example for a CCB: Init OM handle => OK Init Admin Owner handle => OK Init CCB handle => OK Create a object => OK Modify this object => OK Apply CCB => BAD_HANDLE If we handle BAD_HANDLE case use Johan's idea, we need...
-
pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
-
In progress
-
Hi Zoran ! All functions in pyosaf utils decorate by decorate() function in pyosaf/utils/_init_.py. You can see in _init_.py of clm/immoi/immom/log/ntf same as below: saImmOmInitialize = decorate(saImmOm.saImmOmInitialize) saImmOmSelectionObjectGet = decorate(saImmOm.saImmOmSelectionObjectGet) saImmOmDispatch = decorate(saImmOm.saImmOmDispatch) saImmOmFinalize = decorate(saImmOm.saImmOmFinalize) .... All error codes returned handle by decorate() function (decorator of Python). We have been handle...
-
Hi Zoran ! All functions in pyosaf utils decorate by decorate() function in pyosaf/utils/init.py. You can see in init.py of clm/immoi/immom/log/ntf same as below: saImmOmInitialize = decorate(saImmOm.saImmOmInitialize) saImmOmSelectionObjectGet = decorate(saImmOm.saImmOmSelectionObjectGet) saImmOmDispatch = decorate(saImmOm.saImmOmDispatch) saImmOmFinalize = decorate(saImmOm.saImmOmFinalize) .... All error codes returned handle by decorate() function (decorator of Python). We have been handle ERR_BAD_HANDLE...
-
pyosaf: IMM OM module initialized with ERR_BAD_HANDLE
-
In progress
-
Solution: - Remove a preceding underscore character of the initialize method in immom - Does not automatically called initialize() when the module is imported
-
Solution: + ImmObject use exceptions raise without NoneType
-
pyosaf: Invalid exception used in ImmObject (object.py)
-
Solution fix: + ImmObject use exceptions raise without NoneType
-
pyosaf: Invalid exception used in ImmObject (object.py)
-
pyosaf: Invalid exception used in ImmObject (object.py) [#1410]
-
pyosaf: Invalid exception used in ImmObject (object.py)
-
In progress
-
Solution fix: - Remove a preceding underscore character of the initialize method in immom - Does not automatically called initialize() when the module is imported
-
Solution fix: - Remove a preceding underscore character of the initialize method in immom - Does not automatically called initialize() when the module is implemented
-
pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
-
pyosaf: Make pyosaf:::immom::initialize() consistent with other modules [#2533]
-
pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
-
In progress
-
pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
-
imm: Improve ccb error string handling
-
imm: Improve ccb error string handling [#2367]
-
imm: Improve ccb error string handling
-
imm: Fixed memory leak in imm_cfg.c file [#2408]
-
IMM: Fix cppcheck 1.78 memory leak error at tools
-
IMM: Fix cppcheck 1.78 memory leak error at tools
-
IMM: Fix cppcheck 1.78 memory leak error at tools
-
Fix cppcheck 1.78 memory leak error at tools
1