Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stop retrying steps when decisive action failed #1224

Merged
merged 2 commits into from
Nov 20, 2024

Conversation

LawyZheng
Copy link
Collaborator

@LawyZheng LawyZheng commented Nov 20, 2024

Important

Add warning log for failed DecisiveAction in agent_step() in agent.py when execution continues.

  • Logging:
    • Add warning log in agent_step() in agent.py for failed DecisiveAction that does not stop execution.

This description was created by Ellipsis for a5a4f2a. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Reviewed everything up to ba04b71 in 17 seconds

More details
  • Looked at 22 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:801
  • Draft comment:
    The log message for a failed DecisiveAction should indicate that execution will stop, not continue. Consider updating the message to reflect this.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable:
    The comment appears to be incorrect because the code is intentionally logging that execution will not stop after a DecisiveAction fails. The log message aligns with the code's logic, so no change is needed. The comment misunderstands the code's behavior.
    I might be missing some context about the expected behavior of DecisiveAction. However, based on the code, the log message is consistent with the logic implemented.
    The code explicitly logs that execution will not stop, which suggests that this is the intended behavior. The comment seems to misinterpret the code's logic.
    The comment should be deleted because it incorrectly suggests a change to the log message that is consistent with the code's logic.

Workflow ID: wflow_Cn7ib9XBlG31oyIo


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

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Incremental review on a5a4f2a in 10 seconds

More details
  • Looked at 13 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:801
  • Draft comment:
    Consider providing more context in the log message for a failed DecisiveAction. It should explain why execution is not stopped or retried, which can help in debugging.
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The log message for a failed DecisiveAction is not very informative. It should provide more context about why the execution is not stopped or retried.

Workflow ID: wflow_NrE3tLrSgFnDKnea


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

@LawyZheng LawyZheng merged commit 26d96c2 into main Nov 20, 2024
2 checks passed
@LawyZheng LawyZheng deleted the lawy/dont-retry-step-when-decisive-action-failed branch November 20, 2024 03:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants