fix(composer): include transaction processing errors in debug logging #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Moves the
addSwapTransactions()call inside the existing try/catch block inexecute()so that errors during transaction processing are logged with comprehensive failure context before being re-thrown.Previously, only errors from
atc.execute()received debug logging vialogSwapExecutionFailure(). Errors thrown during transaction processing (such as "Failed to process swap transaction at index X") would propagate without any debug context, making it harder to diagnose intermittent issues reported by developers.Changes
addSwapTransactions()call inside the try/catch block inexecute()methodTest Plan