Skip to content

continue syncing issues even if default asset version lookup fails - #2821

Open
refoo0 wants to merge 1 commit into
mainfrom
fix/asset-update-continue-on-default-version-error
Open

continue syncing issues even if default asset version lookup fails#2821
refoo0 wants to merge 1 commit into
mainfrom
fix/asset-update-continue-on-default-version-error

Conversation

@refoo0

@refoo0 refoo0 commented Aug 10, 2026

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: rafi <refaei.shikho@hotmail.com>
Copilot AI lite review requested due to automatic review settings August 10, 2026 11:23

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the asset update flow to avoid aborting the background ticket/issue synchronization when the default asset version lookup fails.

Changes:

  • Downgrades the log from Error to Warn when GetDefaultAssetVersion fails in the Update background task.
  • Removes the early return on default asset version lookup failure (so the subsequent sync call continues).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +399 to 403
// we don't want to return an error here, because we still want to update the asset in the database
slog.Warn("could not get default asset version", "err", err)
}

if err := a.dependencyVulnService.SyncAllIssues(linkedCtx, org, project, asset, defaultAssetVersion, &userAgent); err != nil {
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