Fix authentication errors

[wintonzheng]

Important

Improve error handling by including detailed exception information in logs across multiple files.

• Error Handling:
  • Update failure_reason to include exception details in execute_step() in agent.py, execute_safe() in block.py, and execute_workflow() in service.py.
  • Replace generic exception messages with detailed ones, including exception type and message.
• Imports:
  • Add SkyvernException to imports in context_manager.py.
• Misc:
  • Change error logging to include exception details in register_parameter_value() in context_manager.py.

^{This description was created by for 82d0832. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 82d0832 in 36 seconds

More details

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

1. skyvern/forge/agent.py:573

• Draft comment:
  Consider using consistent capitalization for error messages. Change 'Unexpected error' to 'unexpected error' to match the format used elsewhere.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, the message format should be consistent across the codebase.

2. skyvern/forge/sdk/workflow/models/block.py:283

• Draft comment:
  Consider using consistent capitalization for error messages. Change 'Unexpected error' to 'unexpected error' to match the format used elsewhere.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, the message format should be consistent across the codebase.

3. skyvern/forge/sdk/workflow/service.py:352

• Draft comment:
  Consider using consistent capitalization for error messages. Change 'Unexpected error' to 'unexpected error' to match the format used elsewhere.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, the message format should be consistent across the codebase.

Workflow ID: wflow_U17XrMyWYiF5lxyJ

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on 82d0832 in 53 seconds

More details

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

1. skyvern/forge/agent.py:573

• Draft comment:
  Consider using a consistent format for exception messages. For example, use 'Unexpected error' for all generic exceptions and 'SkyvernException' for specific ones. This will make the logs more uniform and easier to parse.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, there are some areas where the changes could be improved for consistency and clarity.

2. skyvern/forge/sdk/workflow/context_manager.py:176

• Draft comment:
  Consider using a consistent format for exception messages. For example, use 'Unexpected error' for all generic exceptions and 'SkyvernException' for specific ones. This will make the logs more uniform and easier to parse.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, there are some areas where the changes could be improved for consistency and clarity.

3. skyvern/forge/sdk/workflow/models/block.py:283

• Draft comment:
  Consider using a consistent format for exception messages. For example, use 'Unexpected error' for all generic exceptions and 'SkyvernException' for specific ones. This will make the logs more uniform and easier to parse.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, there are some areas where the changes could be improved for consistency and clarity.

4. skyvern/forge/sdk/workflow/service.py:352

• Draft comment:
  Consider using a consistent format for exception messages. For example, use 'Unexpected error' for all generic exceptions and 'SkyvernException' for specific ones. This will make the logs more uniform and easier to parse.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the exception handling to provide more detailed error messages. This is a good practice as it helps in debugging and understanding the context of the error. However, there are some areas where the changes could be improved for consistency and clarity.

Workflow ID: wflow_Ms5bXxmqyVOhazqY

---

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