[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
- **status**: unassigned --> assigned - **assigned_to**: Hieu Nguyen - **Comment**: In progress --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** assigned **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Fri Jul 21, 2017 01:09 PM UTC **Owner:** Hieu Nguyen The module pyosaf/utils/immom has a method with the name initialize(), which is called automatically when the module is implemented. This is inconsistent with other pyosaf modules under utils, which don't call the initialize method automatically when the module is imported. Also, the initialize method in immom has a preceding underscore character, which should be removed to make the method name consistent with the other modules. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
- **status**: assigned --> accepted --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** accepted **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Mon Oct 02, 2017 06:30 AM UTC **Owner:** Hieu Nguyen The module pyosaf/utils/immom has a method with the name initialize(), which is called automatically when the module is implemented. This is inconsistent with other pyosaf modules under utils, which don't call the initialize method automatically when the module is imported. Also, the initialize method in immom has a preceding underscore character, which should be removed to make the method name consistent with the other modules. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
- **status**: accepted --> review - **Comment**: Solution fix: - Remove a preceding underscore character of the initialize method in immom - Does not automatically called initialize() when the module is implemented --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Mon Oct 02, 2017 06:34 AM UTC **Owner:** Hieu Nguyen The module pyosaf/utils/immom has a method with the name initialize(), which is called automatically when the module is implemented. This is inconsistent with other pyosaf modules under utils, which don't call the initialize method automatically when the module is imported. Also, the initialize method in immom has a preceding underscore character, which should be removed to make the method name consistent with the other modules. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)
- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Blocker**: --> False - **Comment**: In progress --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** accepted **Milestone:** future **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Sep 20, 2016 06:04 PM UTC **Owner:** Hieu Nguyen ImmObject uses an invalid way to raise exceptions: >>> a = ImmObject('NonExistingClass') Traceback (most recent call last): File "", line 1, in File "/usr/local/lib/python2.7/dist-packages/pyosaf/utils/immom/object.py", line 63, in __init__ raise TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)
- **status**: accepted --> review - **Comment**: Solution fix: + ImmObject use exceptions raise without NoneType --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** future **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Mon Oct 02, 2017 09:45 AM UTC **Owner:** Hieu Nguyen ImmObject uses an invalid way to raise exceptions: >>> a = ImmObject('NonExistingClass') Traceback (most recent call last): File "", line 1, in File "/usr/local/lib/python2.7/dist-packages/pyosaf/utils/immom/object.py", line 63, in __init__ raise TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)
- **Milestone**: future --> 5.17.10 --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 03:58 AM UTC **Owner:** Hieu Nguyen ImmObject uses an invalid way to raise exceptions: >>> a = ImmObject('NonExistingClass') Traceback (most recent call last): File "", line 1, in File "/usr/local/lib/python2.7/dist-packages/pyosaf/utils/immom/object.py", line 63, in __init__ raise TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2523 pyosaf: IMM OM module initialized with ERR_BAD_HANDLE
- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Comment**: In progress --- ** [tickets:#2523] pyosaf: IMM OM module initialized with ERR_BAD_HANDLE** **Status:** accepted **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:40 PM UTC by Zoran Milinkovic **Last Updated:** Fri Jul 28, 2017 08:20 AM UTC **Owner:** Hieu Nguyen pyosaf does not handle well intialization of IMM OM module. Regardless of error code returned from saImmOmInitialize, in _initialize() function, saImmOmAccessorInitialize is called(). --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2523 pyosaf: IMM OM module initialized with ERR_BAD_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 in this function with stop app and raise exception. if error != eSaAisErrorT.SA_AIS_OK: raise_saf_exception(function, error) Do you have any ideas about this? --- ** [tickets:#2523] pyosaf: IMM OM module initialized with ERR_BAD_HANDLE** **Status:** accepted **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:40 PM UTC by Zoran Milinkovic **Last Updated:** Tue Oct 03, 2017 06:24 AM UTC **Owner:** Hieu Nguyen pyosaf does not handle well intialization of IMM OM module. Regardless of error code returned from saImmOmInitialize, in _initialize() function, saImmOmAccessorInitialize is called(). --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Blocker**: --> False - **Milestone**: future --> 5.17.10 - **Comment**: In progress --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Sun Dec 18, 2016 01:21 PM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 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 keep track all data and all steps of CBB in above case, NOT only re-intialize. That takes many effort to store data and process complex. I think user who know clear their steps. When TRY\_AGAIN error occurred, they can easy rollback their steps. Regards, --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 09:11 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
- **status**: accepted --> wontfix - **Comment**: I set this ticket to "wontfix". If you have any comments, let me know ? --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Wed Oct 04, 2017 03:51 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules
- **status**: review --> fixed - **Comment**: commit dfb0d550adb44e148001beb5237559b3e472fd9c Author: Hieu Nguyen 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 --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** fixed **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Mon Oct 02, 2017 09:12 AM UTC **Owner:** Hieu Nguyen The module pyosaf/utils/immom has a method with the name initialize(), which is called automatically when the module is implemented. This is inconsistent with other pyosaf modules under utils, which don't call the initialize method automatically when the module is imported. Also, the initialize method in immom has a preceding underscore character, which should be removed to make the method name consistent with the other modules. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2524 pyosaf: decorate function does not handle version struct in initialize functions
- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Comment**: In progress --- ** [tickets:#2524] pyosaf: decorate function does not handle version struct in initialize functions** **Status:** accepted **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:44 PM UTC by Zoran Milinkovic **Last Updated:** Fri Jul 28, 2017 08:20 AM UTC **Owner:** Hieu Nguyen decorate() function does not handle version in initialize calls. If initialize function returns ERR_TRY_AGAIN, version struct is populated with the latest version. The next initialize call will not initialize a handle with the required version, but with the latest library version --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2524 pyosaf: decorate function does not handle version struct in initialize functions
- **status**: accepted --> review - **Comment**: 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 --- ** [tickets:#2524] pyosaf: decorate function does not handle version struct in initialize functions** **Status:** review **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:44 PM UTC by Zoran Milinkovic **Last Updated:** Thu Oct 05, 2017 04:54 AM UTC **Owner:** Hieu Nguyen decorate() function does not handle version in initialize calls. If initialize function returns ERR_TRY_AGAIN, version struct is populated with the latest version. The next initialize call will not initialize a handle with the required version, but with the latest library version --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
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/ --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Wed Oct 04, 2017 03:52 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2523 pyosaf: IMM OM module initialized with ERR_BAD_HANDLE
- **status**: accepted --> wontfix - **Comment**: 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 - --- ** [tickets:#2523] pyosaf: IMM OM module initialized with ERR_BAD_HANDLE** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:40 PM UTC by Zoran Milinkovic **Last Updated:** Tue Oct 03, 2017 08:30 AM UTC **Owner:** Hieu Nguyen pyosaf does not handle well intialization of IMM OM module. Regardless of error code returned from saImmOmInitialize, in _initialize() function, saImmOmAccessorInitialize is called(). --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)
- **Type**: defect --> enhancement --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 04:07 AM UTC **Owner:** Hieu Nguyen ImmObject uses an invalid way to raise exceptions: >>> a = ImmObject('NonExistingClass') Traceback (most recent call last): File "", line 1, in File "/usr/local/lib/python2.7/dist-packages/pyosaf/utils/immom/object.py", line 63, in __init__ raise TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)
- **Type**: enhancement --> defect --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Oct 17, 2017 02:16 AM UTC **Owner:** Hieu Nguyen ImmObject uses an invalid way to raise exceptions: >>> a = ImmObject('NonExistingClass') Traceback (most recent call last): File "", line 1, in File "/usr/local/lib/python2.7/dist-packages/pyosaf/utils/immom/object.py", line 63, in __init__ raise TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2681 pyosaf: refactor IMM samples to use new pyosaf utils version 1.0.0
--- ** [tickets:#2681] pyosaf: refactor IMM samples to use new pyosaf utils version 1.0.0** **Status:** accepted **Milestone:** 5.18.01 **Created:** Wed Nov 15, 2017 03:27 AM UTC by Hieu Nguyen **Last Updated:** Wed Nov 15, 2017 03:27 AM UTC **Owner:** Hieu Nguyen 1/ Ticket [#2602](https://sourceforge.net/p/opensaf/tickets/2602/) introduced a new and improved implementation of the pyosaf utils (high-level OpenSAF API Python bindings). 2/ The IMM python samples should be refactored to take advantage of the newly implemented pyosaf utils version 1.0.0 include: + caps + caps-inheritance-impl + imm-listener + imm-listener-inheritance-impl + immadm + immbase.py + immlist + interface-handler + interface-handler-inheritance-impl + ping-pong + ping-pong-inheritance-impl + scale_opensaf + time-reporter + time-reporter-inheritance-impl + tones + tones-inheritance-impl + users + users-inheritance-impl --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2683 pyosaf: improve OI utils use a separate instance OM agent
--- ** [tickets:#2683] pyosaf: improve OI utils use a separate instance OM agent** **Status:** accepted **Milestone:** 5.18.01 **Created:** Thu Nov 16, 2017 08:24 AM UTC by Hieu Nguyen **Last Updated:** Thu Nov 16, 2017 08:24 AM UTC **Owner:** Hieu Nguyen Update the oi agent/implementer/applier to use a separate instance of om agent/accessor instead of using the immom and its deprecated functions. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2683 pyosaf: refactor IMM utils
- **summary**: pyosaf: improve OI utils use a separate instance OM agent --> pyosaf: refactor IMM utils - Description has changed: Diff: --- old +++ new @@ -1 +1,2 @@ -Update the oi agent/implementer/applier to use a separate instance of om agent/accessor instead of using the immom and its deprecated functions. ++ Improve OI utils use a separate instance OM agent ++ Refactor OM utils with Ccb inheritace OmAgent, rename some classes... --- ** [tickets:#2683] pyosaf: refactor IMM utils** **Status:** accepted **Milestone:** 5.18.01 **Created:** Thu Nov 16, 2017 08:24 AM UTC by Hieu Nguyen **Last Updated:** Thu Nov 16, 2017 08:24 AM UTC **Owner:** Hieu Nguyen + Improve OI utils use a separate instance OM agent + Refactor OM utils with Ccb inheritace OmAgent, rename some classes... --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2683 pyosaf: refactor IMM utils
- **status**: accepted --> review --- ** [tickets:#2683] pyosaf: refactor IMM utils** **Status:** review **Milestone:** 5.18.01 **Created:** Thu Nov 16, 2017 08:24 AM UTC by Hieu Nguyen **Last Updated:** Fri Dec 01, 2017 02:04 AM UTC **Owner:** Hieu Nguyen + Improve OI utils use a separate instance OM agent + Refactor OM utils with Ccb inheritace OmAgent, rename some classes... --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2683 pyosaf: refactor IMM utils
- **status**: review --> fixed - **Comment**: commit 842cf55fc3d443998a30181ae944720201f98cec Author: Hieu Nguyen 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... --- ** [tickets:#2683] pyosaf: refactor IMM utils** **Status:** fixed **Milestone:** 5.18.01 **Created:** Thu Nov 16, 2017 08:24 AM UTC by Hieu Nguyen **Last Updated:** Thu Dec 07, 2017 06:50 AM UTC **Owner:** Hieu Nguyen + Improve OI utils use a separate instance OM agent + Refactor OM utils with Ccb inheritace OmAgent, rename some classes... --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets