[soujasK]

Issue number: closes #8661

Summary

Changes

Once a record fails, SqsFifoPartialProcessor short-circuits the remaining records (or the rest of the failed group with skip_group_on_error=True) and converts them with the customer's model before passing them to failure_handler. That conversion was outside any try, so a record that didn't match the model raised out of process() and failed the whole invocation.

Short-circuited records never reach the record handler, so if the model conversion fails they're now registered as event source data classes, like other poison pills. Records that do match the model are still registered as model instances, so fail_messages doesn't change for them.

Tests: a batch with a successful record, a failing record, a record that doesn't match the model in the same group, and a successful record in another group, parametrized over skip_group_on_error. Both cases raised ValidationError before the change and pass after it. tests/functional/batch passes on Linux (Python 3.12), along with ruff, mypy, ty, bandit and xenon.

User experience

Before: a malformed record after a failure fails the whole invocation, so every record is retried, including already processed ones (and, with skip_group_on_error=True, the successful records of other message groups).

After: the malformed record is reported in batchItemFailures along with the other short-circuited records.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud