Skip to content

[AutoDev] FLOW-2251 atlascode: AxiosError:RovoDevFeedbackManager.submitFeedback - #1888

Open
atlassian[bot] wants to merge 1 commit into
mainfrom
FLOW-2251-atlascode-axioserrorrovodevfeedbackmanagersubmitfeedback-c69d1
Open

[AutoDev] FLOW-2251 atlascode: AxiosError:RovoDevFeedbackManager.submitFeedback#1888
atlassian[bot] wants to merge 1 commit into
mainfrom
FLOW-2251-atlascode-axioserrorrovodevfeedbackmanagersubmitfeedback-c69d1

Conversation

@atlassian

@atlassian atlassian Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

🤖 This PR was generated by AutoDev bot.

Action needed: please review, approve, and merge this PR if it is ready. We collect decline feedback to improve quality. Thanks!
Changes needed or questions? Leave comments. Autodev now addresses PR comments every few hours.

This pull request fixes the issue where AxiosError in RovoDevFeedbackManager.submitFeedback was being sent to Sentry and causing SLO errors. Instead of treating these errors as critical, feedback submission failures due to network errors or non-2xx HTTP responses are now logged as warnings, reflecting their transient and expected nature.

Key changes:

Change Area Description
Error Handling Modify submitFeedback to detect AxiosError and log warnings instead of sending errors to Sentry.
Logging Use Logger.warn for Axios network or HTTP errors and unexpected errors during feedback submission.
Tests Add tests covering AxiosError with HTTP status, network errors, and non-Axios errors to verify warnings and user notifications.
Changelog Document the fix in the changelog under version 4.0.32.

This improves reliability by preventing non-critical feedback submission errors from triggering error tracking and alerting systems unnecessarily, while still informing users of submission issues.


Rovo Dev code review: Rovo Dev couldn't review this pull request
Rovo Dev does not review pull requests created by bot accounts.

Replace RovoDevTelemetryProvider.logError() with Logger.warn() in
RovoDevFeedbackManager.submitFeedback to prevent feedback submission
failures (network errors, non-2xx responses) from being reported to
Sentry and triggering SLO errors. These failures are non-critical and
expected in transient failure scenarios.

Co-authored-by: Evan Cook <ecook@atlassian.com>
@atlassian-cla-bot

Copy link
Copy Markdown

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
a393d78c-73d8-4f4d-84ea-500a2d3d8fc3@connect.atlassian.com

Already signed the CLA? To re-check, try refreshing the page.

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.

0 participants