I wasn't sure where to place issues related to the resilient-circuits framework itself, if there is a more appropriate place please let me know.
During some test building of functions and components, if a cafile path is found to be None, for whatever reason (originating from line 468), and is passed into the _setup_stomp function; the call will fail on line 469, seen below. None types don't have attributes to call .strip() or .lower().
|
if cafile.strip().lower() == "false": |
The code appeared to anticipate a possible None type being received, since line 473 does a check for this.
These should probably be swapped to handle the None value being received before working through the other cases.
I wasn't sure where to place issues related to the resilient-circuits framework itself, if there is a more appropriate place please let me know.
During some test building of functions and components, if a cafile path is found to be
None, for whatever reason (originating from line 468), and is passed into the_setup_stompfunction; the call will fail on line 469, seen below.Nonetypes don't have attributes to call.strip()or.lower().resilient-python-api/resilient-circuits/resilient_circuits/actions_component.py
Line 469 in ad42daa
The code appeared to anticipate a possible
Nonetype being received, since line 473 does a check for this.resilient-python-api/resilient-circuits/resilient_circuits/actions_component.py
Line 473 in ad42daa
These should probably be swapped to handle the
Nonevalue being received before working through the other cases.