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

Ensure users are able to track the status of uploads being processed #3229

Open
rohan-at-sentry opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
Area: Report Processing Issues with report processing epic this label is used to mark issues as epics P2: stretch priority <=6
Milestone

Comments

@rohan-at-sentry
Copy link

rohan-at-sentry commented Jan 15, 2025

Problem to Solve

Codecov reports often display partial data on the PR comment and commits tab causing users to perceive them as inaccurate or incomplete, which causes user friction and lack of trust in our reporting.

Additionally, errors are not communicated on the PR comment to a developer unless the notify_error setting is enabled - leading to false angst or comfort as the case may be

Solution

  • Display the comments on PR only after the full report is aggregated - based on when check is complete. note: today, the report shows it's unrelated to the check status, meaning the report may show before/after the check is done.

    • Inform users of an error: If an error occurs, display:
      • Contextual messaging explaining the issue
      • Available data with clear copy indicating it may be incomplete or inaccurate
      • Deprecates notify_error and becomes default behavior
  • Display Coverage data and files changed/indirect changes sections on commits page only after the full report is aggregated.

    • Inform users of error. If an error occurs display
      • Upload count (x successfully processed, y failed)

view designs PR comment

view designs commits page

@rohan-at-sentry
Copy link
Author

This is a focused epic implementation epic spawning from a large discover effort spanning a host of issues, chiefly

the above issues can be closed out in favor of this current one, just linking here for good bookkeeping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Report Processing Issues with report processing epic this label is used to mark issues as epics P2: stretch priority <=6
Projects
None yet
Development

No branches or pull requests

5 participants