fix: use caught error variable in reportProgress catch block

[davisthedev]

🔗 Linked issue

76

❓ Type of change

• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The catch block was using error (from validateProcessedBytes) instead of
err (the caught exception), causing undefined to be emitted when
reportProgress throws, which crashes the error handler.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[davisthedev]

Apologies for missing any steps for your process. I came across this working on a project and it was causing my api to crash.

[thetutlage]

Is it possible for you to write a test that helps us reproduce this issue? Or maybe share a scenario I could use to test it myself

[davisthedev]

@thetutlage Can I open a pull request to merge this into 10.x version?

[thetutlage]

Sure, please do that.

[davisthedev]

ok, i opened: #77