Follow-up from "Add real-time ci status to pipeline header and refactor previous code"

The following discussion from !186434 (merged) should be addressed:

• @psjakubowska started a discussion: (+4 comments)

  I think I've found an issue that might be a side effect of your MR.

  We've noticed an increased number of errors in the Source Code Sentry dashboard after last weekend, compared to the usual numbers we get for those days. That aligns with the time when your MR was deployed (see our Sentry dashboard for the last 14 days).

  I've also noticed the issue locally. I get a repeated call for lastCommit query and a console error, despite the feature flag returning false and no pipeline data to show:

  header	header

  When you inspect one of the errors in Sentry, you can see that the last commit info is queried every 30 seconds or so (see Breadcrumbs section of one of the errors). This is now at ~60k events since the issue started to happen.

  I suspect you might need to tighten the conditions a bit 🙂

  Agree. Let's add some logging to LastCommit component with:

  import { logError } from '~/lib/logger';
  import * as Sentry from '~/sentry/sentry_browser_wrapper';
  ...
  logError(`Unexpected error while fetching projectInfo query`, error);
  Sentry.captureException(error);

  I'm going to create a follow-up from this thread and address it before the end of the week.