GitHub authentication timeout preventing pull request creation in Vercel

Logs

Failed to load resource: the server responded with a status of 404 ()

[open-vsx.org/vscode/…rcel-theme/latest:1](http://open-vsx.org/vscode/%E2%80%A6rcel-theme/latest:1) Failed to load resource: the server responded with a status of 404 ()

bb1c6cf47ae89d62.js?…NZHPqZ54ERxuSPWCC:5 [SnapshotRenderer] iframe load event - assuming ready

75973_next_dist_comp…ex_ab95c7de.js:2303 Image with src “/images/hero-barbershop.jpg” was detected as the Largest Contentful Paint (LCP). Please add the `loading=“eager”` property if this image is above the fold.  
Read more: https://nextjs.org/docs/app/api-reference/components/image#loading

log.ts:460 ERR Timed out waiting for authentication provider ‘github’ to register.: Error: Timed out waiting for authentication provider ‘github’ to register.  
at Jze.G (https://sb-7g18ll02jeww.vercel.run/stable-a20d001…/static/out/vs/code/browser/workbench/workbench.js:607:67633)  
at async Jze.getSessions (https://sb-7g18ll02jeww.vercel.run/stable-a20d001…/static/out/vs/code/browser/workbench/workbench.js:607:64650)  
at async Jze.getAccounts (https://sb-7g18ll02jeww.vercel.run/stable-a20d001…/static/out/vs/code/browser/workbench/workbench.js:607:64407)  
at async c$.C (https://sb-7g18ll02jeww.vercel.run/stable-a20d001…/static/out/vs/code/browser/workbench/workbench.js:518:11542)  
at async c$.z (https://sb-7g18ll02jeww.vercel.run/stable-a20d001…/static/out/vs/code/browser/workbench/workbench.js:518:11201)  
at async c$.y (https://sb-7g18ll02jeww.vercel.run/stable-a20d001…/static/out/vs/code/browser/workbench/workbench.js:518:10957)

Problem

Please help. Button is in disabled state: “No changes to publish”

There are indeed changes.

What I’ve Tried

  1. Reconnect to github
  2. New branch
  3. Restart box/vm

Love this feature but definitely a defect and needs a jira ticket lol. Based on logs its probably just github service down with the 404. I was having issues accessing parts of github earlier not sure if its related. Let us know if you find out anything! Also would be nice if you allowed custom GitLab instances for times like these.

It seems like this was related to the GitHub incident yesterday. If you are still seeing this, let us know.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.