Fix nil txReceipt handling in SetOutputVarForStep

[devin-ai-integration]

Fix nil txReceipt handling in SetOutputVarForStep

Description

This PR fixes the test failure in PR #215 by properly handling nil txReceipt in the ContractWriteProcessor's SetOutputVarForStep method. The issue was that the code was trying to include txReceipt in output variables without checking if it was nil first, which could cause a nil pointer dereference.

Changes

• Updated SetOutputVarForStep to only include txReceipt in output variables if it's not nil

Testing

The fix addresses the failing test TestContractWriteSimpleReturn in the core/taskengine package.

Related Issues

Fixes the test failure in PR #215: https://github.com/AvaProtocol/EigenLayer-AVS/actions/runs/14543855857/job/40806468997?pr=215

Link to Devin run

https://app.devin.ai/sessions/8fedac6730214293bcba154bf20912c2

Requested by: Chris Li (chris@avaprotocol.org)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[Copilot]

Pull Request Overview

This PR fixes an issue in the ContractWriteProcessor by ensuring that txReceipt is only added to the output variables if it is not nil, preventing a potential nil pointer dereference.

• Introduces a local map (outputVars) to construct output variables.
• Conditionally adds txReceipt to outputVars based on a nil check.
• Updates the call to SetOutputVarForStep with the refined outputVars.

Comments suppressed due to low confidence (1)

core/taskengine/vm_runner_contract_write.go:181

• The variable 'txReceipt' is not defined in this scope; it appears you intended to check 'outputData.ContractWrite.TxReceipt'.

if txReceipt != nil {