fix(error-handling): prevent infinite recursion when errorHandler throws

[ifer47]

Summary

• Add isHandlingError guard to prevent infinite recursion when the custom error handler itself throws an error
• Previously, if config.errorHandler threw, it would trigger handleError again, which calls the error handler again, causing infinite recursion and Maximum call stack size exceeded
• The guard ensures that if handleError is called while already handling an error, it returns early instead of re-entering the error handling flow

Problem

When a custom config.errorHandler throws an error, the following chain occurs:

1. invokeWithErrorHandling catches the original error
2. Calls handleError
3. handleError calls globalHandleError
4. globalHandleError calls config.errorHandler
5. If errorHandler throws, it calls logError
6. If logError or any code path leads back to invokeWithErrorHandling, the cycle repeats
7. Result: RangeError: Maximum call stack size exceeded

Changes

• Added module-level isHandlingError flag
• Set flag to true at the start of handleError
• Early return with popTarget() if already handling an error
• Reset flag to false in the finally block
• Added test case to verify the fix

Closes #13241

🤖 Generated with Claude Code Best