Unable to access a PR

[rsp4jack]

🏷️ Discussion Type

Bug

Body

FluidSynth/fluidsynth#982

It says:

Unable to load page.
The page is unavailable due to a system error. Try reloading the page, or if the problem persists, contact support.

I submitted a support ticket and they closed it immediately.

I found this in the console:

React Router caught the following error during render TypeError: can't access property "split", e is null
    o utils.ts:38
    WJ9 path.ts:184
    ek PullRequestBranchName.tsx:21
    React 8
    _ scheduler.production.js:151
    4477 scheduler.production.js:199
    b wp-runtime-dd9cf7b72ceacc71.js:2
    169982 index.js:4
    b wp-runtime-dd9cf7b72ceacc71.js:2
    31247 React
    b wp-runtime-dd9cf7b72ceacc71.js:2
    205338 React
    b wp-runtime-dd9cf7b72ceacc71.js:2
    722484 react-core-8141ae140cbb8e0f.js:2
    b wp-runtime-dd9cf7b72ceacc71.js:2
    715331 react-core-8141ae140cbb8e0f.js:3
    b wp-runtime-dd9cf7b72ceacc71.js:2
    664083 pull-requests-860b95f443cb627b.js:2
    b wp-runtime-dd9cf7b72ceacc71.js:2
    <anonymous> pull-requests-860b95f443cb627b.js:2
    O on_chunk_loaded:27
    <anonymous> pull-requests-860b95f443cb627b.js:2
    a jsonp_chunk_loading:71
    <anonymous> jsonp_chunk_loading:90
    <anonymous> wp-runtime-dd9cf7b72ceacc71.js:2
react-core-8141ae140cbb8e0f.js:6:4855

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kamrullab]

The console error (TypeError: can't access property "split", e is null) makes this look more like a frontend issue than something wrong with the PR itself.

A couple of things I'd try just to rule out local issues:

• Open the PR in an incognito/private window or a different browser.
• Try with browser extensions disabled and clear the GitHub site cache.

If it still fails, it's probably not something you can fix yourself. The stack trace points to GitHub's pull request page, so this may be a regression or an edge case triggered by that specific PR. Since your support ticket was closed without resolving the issue, hopefully someone from the GitHub team can take another look.

The console output you included should be helpful for debugging.

[initial-d]

I can reproduce a useful clue from the public API side.

gh pr view 982 --repo FluidSynth/fluidsynth can still read the PR, but the PR metadata currently looks like this:

{
  "state": "MERGED",
  "isCrossRepository": true,
  "headRefName": "master",
  "headRepository": null,
  "headRepositoryOwner": "sykhro"
}

That matches the frontend stack trace pretty well: the failing component is PullRequestBranchName.tsx, and the error is trying to call split on null. So this does not look like a permissions problem or a broken PR. It looks like a GitHub web UI edge case where the PR page assumes the head repository / branch display value is present, but for this old cross-repository merged PR the head repository is no longer available.

A more actionable support packet would be:

1. The PR URL: [RFC] PipeWire audio driver FluidSynth/fluidsynth#982
2. The console error you already pasted.
3. This API clue: public PR data is readable, but headRepository is null while the page crashes in the branch-name renderer.
4. A note that browser/cache/extensions are unlikely to be the root cause because the underlying PR data has a null branch/repository field.

Temporary workaround: the PR can still be inspected through API/CLI, for example:

gh pr view 982 --repo FluidSynth/fluidsynth
gh pr diff 982 --repo FluidSynth/fluidsynth
gh pr checkout 982 --repo FluidSynth/fluidsynth

The actual fix likely has to be on GitHub's side: render a fallback such as unknown/deleted head repository instead of crashing when the head repository value is missing.

[roke-julian-lockhart]

@initial-d, I am able to corroborate this. I have submitted support.github.com/ticket/personal/0/4584377#tc-51538911154836, wherein I stated that I am consistently unable to access solely hardinfo2/hardinfo2/pull/204, because I observe “The page is unavailable due to a system error”, regardless of browser:

However, the PR definitely exists:

PowerShell 7.6.3-0-ga1994c19a0badf524d714cacffe7986c5c8613c6
PS /home/beedell.roke_julian_lockhart> gh api graphql `
>>   -f query='query($id:ID!){node(id:$id){...on PullRequest{url}}}' `
>>   -F id='PR_kwDOLP0Hw87E2_fb' `
>>   --jq '.data.node.url'
https://github.com/hardinfo2/hardinfo2/pull/204

The relevant logs certainly appear to corroborate yours:

fetch-patch.ts:11  GET https://github.com/in-product-messaging/budget-threshold-banner?organization=hardinfo2 net::ERR_ABORTED 401 (Unauthorized)
(anonymous) @ fetch-patch.ts:11
(anonymous) @ include-fragment.ts:10
(anonymous) @ include-fragment-element.js:193
await in (anonymous)
(anonymous) @ include-fragment-element.js:171
(anonymous) @ include-fragment-element.js:137
attributeChangedCallback @ include-fragment-element.js:84
define @ include-fragment-element.js:41
(anonymous) @ include-fragment-element-define.js:4
b @ wp-runtime-dd9cf7b72ceacc71.js:2
266060 @ 30058-a587bf91d659fae4.js:2
b @ wp-runtime-dd9cf7b72ceacc71.js:2
830888 @ github-elements-9c0e90e6da2c718a.js:2
b @ wp-runtime-dd9cf7b72ceacc71.js:2
(anonymous) @ github-elements-9c0e90e6da2c718a.js:2
(anonymous) @ on_chunk_loaded:27
(anonymous) @ github-elements-9c0e90e6da2c718a.js:2
(anonymous) @ jsonp_chunk_loading:71
(anonymous) @ jsonp_chunk_loading:90
(anonymous) @ wp-runtime-dd9cf7b72ceacc71.js:2
chunk-4N6VE7H7.mjs:6111 React Router caught the following error during render TypeError: Cannot read properties of null (reading 'split')
    at o (utils.ts:38:15)
    at WJ9 (path.ts:184:28)
    at ek (PullRequestBranchName.tsx:21:16)
    at a8 (react-dom-client.production.js:4351:21)
    at oF (react-dom-client.production.js:6497:15)
    at oQ (react-dom-client.production.js:7473:14)
    at sS (react-dom-client.production.js:11305:14)
    at react-dom-client.production.js:11182:37
    at sk (react-dom-client.production.js:11183:1)
    at su (react-dom-client.production.js:10728:40)
componentDidCatch @ chunk-4N6VE7H7.mjs:6111
(anonymous) @ react-dom-client.production.js:5955
az @ react-dom-client.production.js:4216
aO @ react-dom-client.production.js:4226
o3 @ react-dom-client.production.js:8636
iu @ react-dom-client.production.js:9046
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9018
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9018
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9014
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9083
iw @ react-dom-client.production.js:9904
iu @ react-dom-client.production.js:9050
sR @ react-dom-client.production.js:11660
sE @ react-dom-client.production.js:11520
sc @ react-dom-client.production.js:10920
su @ react-dom-client.production.js:10826
sY @ react-dom-client.production.js:12078
_ @ scheduler.production.js:151
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
_ @ scheduler.production.js:187
postMessage
(anonymous) @ scheduler.production.js:202
(anonymous) @ scheduler.production.js:325
sX @ react-dom-client.production.js:12055
sK @ react-dom-client.production.js:11978
(anonymous) @ react-dom-client.production.js:12095
chunk-4N6VE7H7.mjs:6111 React Router caught the following error during render TypeError: Cannot read properties of null (reading 'split')
    at o (utils.ts:38:15)
    at WJ9 (path.ts:184:28)
    at ek (PullRequestBranchName.tsx:21:16)
    at a8 (react-dom-client.production.js:4351:21)
    at oF (react-dom-client.production.js:6497:15)
    at oQ (react-dom-client.production.js:7473:14)
    at sS (react-dom-client.production.js:11305:14)
    at react-dom-client.production.js:11182:37
    at sk (react-dom-client.production.js:11183:1)
    at su (react-dom-client.production.js:10728:40)
componentDidCatch @ chunk-4N6VE7H7.mjs:6111
/in-product-messaging/budget-threshold-banner?organization=hardinfo2:1  Failed to load resource: the server responded with a status of 401 ()

I would attempt to corroborate that JSON, but cli/cli/issues/8215#issuecomment-1770191220 prevents me, without knowing what field to query.

[rsp4jack]

I can confirm that this is fixed by GitHub.

[roke-julian-lockhart]

@rsp4jack, likewise.