I ran into an issue today after splitting and renaming a repo (

galewings-api

-->

gale-wings--api

+ moving some code to a new

gale-wings--data

repo). I went to sync the new repo, but when I try to edit synced repos, the page crashes (see attached video). I can still see the old repo name (

galewings-api

) in the synced repositories list, but am unable to remove it so it's kind of a chicken-egg situation. What I've tried • Refreshing the page (including hard refresh to clear cache) • Logging out of graphite and logging back in • removing graphite from my github account and reconnecting ◦ Same repos appear from previous integration even though I didn't grant graphite access to those when reconnecting: Tailroom, dj-meyers, and more appear when they no longer should (see attached image) Let me know if there's any other info I can provide. I'm able to work around this in the meantime using vanilla github PRs, but I like using Graphite for a reason 😆 Maybe some helpful information from the console:

TypeError: e is undefined
  at 4128-b8df48111dcaaf25.js:1:18404

Caught by Graphite’s ErrorBoundary; component stack shows the crash inside the settings sidebar/article render path (frames in

52177-c3e9982d49c2698d.js

, terminating in the

4128-b8df48111dcaaf25.js

chunk).

Exact same issue here, can't seem to do anything which requires listing repos, so the app is basically useless. Asked claude to investigate because I thought it might be an account state issue I can correct somehow and this is the feedback: --- The crash is a missing argument bug. When you click the repo selector on the Merge Queues page, a component called

aB

(the repo dropdown) renders and unconditionally calls

useListHostedRepos()

with no arguments. That hook immediately tries to destructure

{ namespace }

from its argument, which is

undefined

, causing the

TypeError

that React's ErrorBoundary catches and displays as "We've encountered an error." Why

enabled: false

doesn't save it: The developer gated the feature with a Statsig flag (

"enable_origin_section_query"

) using

{ enabled: T }

on the react-query call. But React's rules of hooks mean the hook function always runs —

enabled

only skips the network request, not the hook call itself. So the crash happens unconditionally whenever the dropdown opens, regardless of the flag's value. The fix needs to happen in two places: 1. At the call site — pass the correct namespace: change

(0,aA.V)()

to

(0,aA.V)({ namespace: <org> })

, where the org comes from the

fixedOrg

or

preselectedOrg

props already available in the component. 2. In the hook itself — add a default parameter

function useListHostedRepos(e = {})

as a defensive safeguard against future accidental no-arg calls.

Hey all, Thanks for the report. This matches an active incident we’re tracking and the root cause has been identified and a fix is on the way. We expect it to be resolved with the next production deploy soon. I’ll keep this thread linked to the incident and follow up once the fix is live.

Just letting you know I was able to update my repos just now. Not sure if it's related to your work on the incident or a daily cron cleanup, but I'm unblocked now. Thanks for the response!

Happy to support! Just confirming the incident has been officially reported as resolved by our engineering team.