Skip to content

fix(agent): include resource details in update errors - #183

Open
slashburygin wants to merge 1 commit into
masterfrom
log
Open

fix(agent): include resource details in update errors#183
slashburygin wants to merge 1 commit into
masterfrom
log

Conversation

@slashburygin

@slashburygin slashburygin commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Summary by Sourcery

Bug Fixes:

  • Ensure resource update failures log both the resource type and UUID for easier debugging.

@slashburygin
slashburygin requested a review from a team as a code owner July 24, 2026 12:40
@sourcery-ai

sourcery-ai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Improves logging for resource update failures by including the resource kind/capability and UUID in exception messages for easier debugging of agent update errors.

File-Level Changes

Change Details Files
Improve exception logging when updating capabilities to include both the capability identifier and resource UUID.
  • Wrap the LOG.exception call for resource update failures across multiple lines for readability.
  • Extend the logged message to explicitly include the resource UUID in the error text while still passing capability and UUID as arguments.
gcl_sdk/agents/universal/services/agent.py
Improve exception logging when updating resource facts to include both resource kind and UUID in error messages.
  • Replace the previous generic LOG.exception message with a formatted string that includes both the resource kind and UUID.
  • Ensure the correct variables (kind and res_uuid) are passed as arguments to the log message instead of an undefined or incorrect identifier.
gcl_sdk/agents/universal/services/agent.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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.

1 participant