step output is very noisy as logs and cost us a lot in logging

[wintonzheng]

🚀	This description was created by Ellipsis for commit 3835df6

Summary:

Reduce log verbosity by excluding output field from log comparisons and updates in update_step and handle_completed_step functions in skyvern/forge/agent.py.

Key points:

• File Modified: skyvern/forge/agent.py
• Function Modified: update_step
  • Exclude output field from log comparisons and updates.
• Function Modified: handle_completed_step
  • Remove output field from log updates when marking steps as completed or creating next steps.

---

Generated with ❤️ by ellipsis.dev

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 3835df6 in 47 seconds

More details

• Looked at 30 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. skyvern/forge/agent.py:1389

• Draft comment:
  Excluding the 'output' field from logging in update_step might reduce visibility into critical changes. Consider logging outputs conditionally based on a debug or verbose setting to balance between verbosity and necessary insight.
• Reason this comment was not posted:
  Confidence of 30% on close inspection, compared to threshold of 50%.

Workflow ID: wflow_hWBqD2grNSkKsrKi

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[github-actions]

This pull request is stale because it has been open for 14 days with no activity.