Jobs list error ; Closes #262

[pranjalg1331]

Description

I have corrected the key value error and added a condition to check it the playbook_to_execute field is iterable.
Please include a summary of the change.

Related issues

Please add related issues.

Type of change

Please delete options that are not relevant.

• [x ] Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

• [ x] The pull request is for the branch develop
• I have added tests in the Tests folder.
• The tests gave 0 errors.
• [ x] Black gave 0 errors.
• [ x] Flake gave 0 errors.
• I squashed the commits into a single one. (optional, they will be squashed anyway by the maintainer)

please follow these rules

• If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
• Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review

Real World Example

Please delete if the PR is for bug fixing.
Otherwise, please provide the resulting raw JSON of a finished analysis (and, if you like, a screenshot of the results). This is to allow the maintainers to understand how the analyzer works.

[mlodic]

thank for finding the issue but actually this does not fix the problem cause the key is being accessed anyway. You should write in to safe check it

[pranjalg1331]

I have added a further check in case the key is not present. Here is the resultant output.

[mlodic]

Suggested change

	el.get("playbook_to_execute", [])
	if el.get("playbook_to_execute")
	else []
	el["playbook_to_execute"]
	if "playbook_to_execute" in el
	else []

[mlodic]

this is the best way to do that

[pranjalg1331]

@mlodic, sir this would not check if el["playbook_to_execute"] is iterable or not.

[pranjalg1331]

So when it is null, we will get an error.

[mlodic]

oh good catch. I think that this is an imperfection of the APIs because either you have the key populated or you don't have that key at all. Having the key available and set as null does not make any sense, it is wasted data and causes problems in handling the data, like the one you found. So well, we have to stick with your solution. Thank you