fix: Gracefully handle missing repositories on pull page#3995
Open
sentry[bot] wants to merge 1 commit into
Open
fix: Gracefully handle missing repositories on pull page#3995sentry[bot] wants to merge 1 commit into
sentry[bot] wants to merge 1 commit into
Conversation
Author
❌ 4 Tests Failed:
View the top 3 failed test(s) by shortest run time
|
Author
Bundle ReportChanges will increase total bundle size by 85 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: gazebo-production-esmAssets Changed:
Files in
view changes for bundle: gazebo-production-systemAssets Changed:
Files in
|
❌ 4 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Collaborator
✅ Deploy preview for gazebo ready!Previews expire after 1 month automatically.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the issue of multiple "Not Found Error" events being logged in Sentry when a repository is not found on a pull request page, particularly for GitLab subgroup repositories.
Problem:
Previously, when the GraphQL API returned
__typename: 'NotFoundError'for a repository (e.g.,dmarcian:core/dmarcian), multiple frontend hooks on the pull request page (such asusePullBundleComparisonList,useRepoOverview, andPullPageDataQueryOpts) would independently callrejectNetworkError. This led to a cascade of Sentry events for the same underlying issue.Root Cause:
Each hook was designed to reject its promise upon receiving a
NotFoundErrorfrom the GraphQL API. The mainPullRequestPagecomponent was not short-circuiting early enough to prevent child components and their associated data-fetching hooks from executing when the repository was definitively not found.This approach ensures that only a single, controlled
NotFoundstate is reached, preventing unnecessary API calls and Sentry noise.Code Example
No specific code examples are provided in the description.
Notable Changes
src/pages/PullRequestPage/queries/PullPageDataQueryOpts.tsx: Instead of callingrejectNetworkErrorwhen aNotFoundErroris encountered, it now returns a sentinel object{ notFound: true, ... }. This prevents an immediate Sentry log and allows for graceful handling.src/pages/PullRequestPage/PullRequestPage.tsx: The mainPullRequestPagecomponent's guard condition was updated to check fordata?.notFound(or!data?.pull). Iftrue, it immediately renders the<NotFound />component. This ensures that child components and their hooks (likeusePullBundleComparisonList) are never mounted or executed when the repository is missing.src/services/repo/useRepoOverview.ts: Similar toPullPageDataQueryOpts,useRepoOverviewnow returns{ notFound: true, ... }instead of rejecting when aNotFoundErroris received. This allows thePullRequestPageto detect a missing repository even earlier, beforePullPageDataQueryOptsis called, further reducing redundant API calls and Sentry errors.Screenshots
No screenshots are applicable for this change.
Link to Sample Entry
No sample entry link is provided in the description.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Fixes GAZEBO-17ZE