Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #334116
Closed
Open
Issue created Jun 20, 2021 by charlie ablett@cablett🛠Maintainer

Alert on MRs `Something went wrong on our end while loading the code quality diff`

Overview

The following red banner is appearing on MRs:

image

Internal thread: https://gitlab.slack.com/archives/CETG54GQ0/p1623239652216500

This banner used to be blank, which was fixed by !63230 (merged)

I was able to reproduce this by switching to and from an MR tab. Whenever I switched focus to the MR tab, the banner appeared.

Current Status

The feature flag to disable this feature was flipped so it is off by default on Gitlab.com as of 2021-06-21 and will be picked into 14.0.1.

Proposal

  1. This should be changed to fail silently as any alert just interferes with the Code Review workflow
  2. This also matches with case #3 (closed) in issue with #327751 (closed) so not displaying anything until that processing is done would also fix this.
Edited Jun 22, 2021 by James Heimbuck
Assignee
Assign to
Time tracking