fix for issue#673

[Ravisaketi]

Proposed changes

Added error handling in src/wq/ql/notify.py fix for issue #673

Types of changes

What types of changes does your code introduce to the project? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Maintenance (update of libraries or other dependences)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING doc
• [x] I have signed the CLA
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] I have run all the existing tests locally (not just those related to my feature) and there are no errors
• [x] After the last push to the PR branch, I have run the lint script locally and there are no changes to the code base
• [x] I have updated the RELEASE NOTES
• [ ] I have added necessary documentation (if appropriate)
• [x] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

"Martel Open Source Software Individual Contributor License Agreement"

"Contributing to QuantumLeap"

"QuantumLeap Release Notes"

[github-actions[bot]]

CLA Assistant Lite bot All contributors have signed the CLA ✍️

[c0c0n3]

@Necravisaketi thanks for the initial change set, but I think we need something different---see my review comments. Not your fault, the TODO comment was way too cryptic, my bad!!

[Ravisaketi]

Hi, @c0c0n3 Thank you for your valuable feedback. I will update this pr as you said.

[c0c0n3]

@Necravisaketi if there's nothing else you'd like to push to this branch I think we're ready to merge? Can you confirm so I can merge this PR?

Notice Coveralls reports a drop of a whooping 10.5% in code coverage. I had a look at the report, not a chance in hell it's accurate---at least not w/r/t your changes. In fact, the report says coverage dropped in most modules, even outside of WQ, so this drop is obviously unrelated to your change set.

[Ravisaketi]

@Necravisaketi if there's nothing else you'd like to push to this branch I think we're ready to merge? Can you confirm so I can merge this PR?

Notice Coveralls reports a drop of a whooping 10.5% in code coverage. I had a look at the report, not a chance in hell it's accurate---at least not w/r/t your changes. In fact, the report says coverage dropped in most modules, even outside of WQ, so this drop is obviously unrelated to your change set.

Hi @c0c0n3 Please merge this PR. Thank you.