fix: check for None in SAS eval input

[lbux]

Related Issues

• fixes SASEvaluator returns score even when predicted_answers contains None #7842

Proposed Changes:

Properly raises ValueError if any input in input list for predicted_answers contains None.

How did you test it?

Checked for Value Error raise.

Notes for the reviewer

N/A

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 9606948606

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 8 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.002%) to 90.173%

---

Files with Coverage Reduction	New Missed Lines	%
components/evaluators/sas_evaluator.py	8	63.33%

Totals
Change from base Build 9600865720:	0.002%
Covered Lines:	7020
Relevant Lines:	7785

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 9612305431

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 81 unchanged lines in 5 files lost coverage.
• Overall coverage decreased (-0.2%) to 89.98%

---

Files with Coverage Reduction	New Missed Lines	%
document_stores/in_memory/document_store.py	1	97.87%
core/component/component.py	2	98.28%
components/evaluators/sas_evaluator.py	8	63.33%
utils/hf.py	20	83.89%
components/validators/json_schema.py	50	0.0%

Totals
Change from base Build 9600865720:	-0.2%
Covered Lines:	6717
Relevant Lines:	7465

---

💛 - Coveralls

[davidsbatista]

just a small comment on the release note other than that LGTM, thanks for contributing!