Fix issue #6262: [Bug]: "Success/failure" behavior is not consistent for file reading and editing

[openhands-agent]

This pull request fixes #6262.

The changes made directly address the core issue and implement the requested functionality:

1. The code now properly handles file read/edit operations by modifying the addAssistantAction and addAssistantObservation functions to show appropriate success/failure indicators for these operations, matching the behavior seen with Python and Bash commands.

2. Success detection was implemented by checking for content presence and absence of error messages in the operation results, providing clear visual feedback through indicators.

3. The ExpandableMessage component was updated to show success/failure indicators consistently, even when there's no headline, ensuring uniform behavior across all action types.

These changes should result in:

• Success cases showing "Read/Edited the contents of a file" with a green check
• Failure cases showing the same message with a red X
• Consistent behavior matching the command execution indicators

The modifications directly implement the expected behavior outlined in the issue description, transforming the inconsistent feedback into a standardized system for all file operations.

Automatic fix generated by OpenHands 🙌

---

To run this PR locally, use the following command:

docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:f33afe9-nikolaik   --name openhands-app-f33afe9   docker.all-hands.dev/all-hands-ai/openhands:f33afe9

[neubig]

@openhands-agent frontend linting is failing. Please run the frontend components of lint.yml and make adjustments till they pass. Once they pass, re-run fe-unit-tests.yml to make sure that tests still pass.

[openhands-agent]

OpenHands started fixing the pr! You can monitor the progress here.

[openhands-agent]

Overview of Changes:

✘ Core Issues Not Resolved:

• Inconsistent success/failure indicators remain unfixed
• Inconsistent messaging for file operations not addressed
• No new tests added as requested

✓ Only Addressed:

• Code formatting/linting improvements

Remaining Work Needed:

1. Implement proper success indicators for file operations
2. Implement proper failure indicators for file operations
3. Standardize messaging across success/failure cases
4. Add tests demonstrating correct behavior

Summary: The changes only addressed code formatting while the main functional issues remain unresolved. A more comprehensive fix is still required.