Just having some CI issues with the test. Seems to be hanging and timing out?

I had a little trouble following the flow of logic in theProxyContext, and so I tried to simplify it a bit. I could easily be missing something - it's a complicated feature and you've done a great job with it - but I'm wondering if we can simplify our use of React state a little bit. This might make testing easier, as well. I'm happy to walk through this on a call!

interface Proxy {  selectedProxy: Region | undefined  preferredPathAppURL: string  preferredWildcardHostname: string}export interface ProxyContextValue {  proxy: Proxy  proxies?: Region[]  isFetched: boolean  isLoading: boolean  error?: Error | unknown  getSavedProxy: () => void  proxyLatencies: Record<string, ProxyLatencyReport>  setProxy: (selectedProxy: Region) => void  clearProxy: () => void}export const ProxyContext = createContext<ProxyContextValue | undefined>(  undefined,)/** * ProxyProvider interacts with local storage to indicate the preferred workspace proxy. */export const ProxyProvider: FC<PropsWithChildren> = ({ children }) => {  const dashboard = useDashboard()  const experimentEnabled = dashboard?.experiments.includes("moons")  const [proxy, setProxy] = useState<Proxy>(    getPreferredProxy([], loadUserSelectedProxy()),  )  const {    data: proxiesResp,    error: proxiesError,    isLoading: proxiesLoading,    isFetched: proxiesFetched,  } = useQuery({    queryKey: ["get-proxies"],    queryFn: getWorkspaceProxies,  })  const proxyLatencies = useProxyLatency(proxiesResp)  // This useEffect ensures the proxy to be used is updated whenever the state changes.  // This includes proxies being loaded, latencies being calculated, and the user selecting a proxy.  useEffect(() => {    setProxy(      getPreferredProxy(        proxiesResp?.regions ?? [],        loadUserSelectedProxy(),        proxyLatencies,      ),    )  }, [proxiesResp, proxyLatencies])  return (    <ProxyContext.Provider      value={{        getSavedProxy: () => loadUserSelectedProxy(),        proxyLatencies: proxyLatencies,        proxy: experimentEnabled          ? proxy          : {              // If the experiment is disabled, then call 'getPreferredProxy' with the regions from              // the api call. The default behavior is to use the `primary` proxy.              ...getPreferredProxy(proxiesResp?.regions || []),            },        proxies: proxiesResp?.regions,        isLoading: proxiesLoading,        isFetched: proxiesFetched,        error: proxiesError,        // These functions are exposed to allow the user to select a proxy.        setProxy: (proxy: Region) => {          // Save to local storage to persist the user's preference across reloads          saveUserSelectedProxy(proxy)          // Set the state for the current context.          getPreferredProxy(proxiesResp?.regions ?? [], loadUserSelectedProxy())        },        clearProxy: () => {          // Clear the user's selection from local storage.          clearUserSelectedProxy()          // Set the state for the current context.          getPreferredProxy(proxiesResp?.regions ?? [])        },      }}    >      {children}    </ProxyContext.Provider>  )}

I had a little trouble following the flow of logic in theProxyContext, and so I tried to simplify it a bit. I could easily be missing something - it's a complicated feature and you've done a great job with it - but I'm wondering if we can simplify our use of React state a little bit. This might make testing easier, as well. I'm happy to walk through this on a call!

interfaceProxy{selectedProxy:Region|undefinedpreferredPathAppURL:stringpreferredWildcardHostname:string}exportinterfaceProxyContextValue{proxy:Proxyproxies?:Region[]isFetched:booleanisLoading:booleanerror?:Error|unknowngetSavedProxy:()=>voidproxyLatencies:Record<string,ProxyLatencyReport>setProxy:(selectedProxy:Region)=>voidclearProxy:()=>void}exportconstProxyContext=createContext<ProxyContextValue|undefined>(undefined,)/** * ProxyProvider interacts with local storage to indicate the preferred workspace proxy. */exportconstProxyProvider:FC<PropsWithChildren>=({ children})=>{constdashboard=useDashboard()constexperimentEnabled=dashboard?.experiments.includes("moons")const[proxy,setProxy]=useState<Proxy>(getPreferredProxy([],loadUserSelectedProxy()),)const{data:proxiesResp,error:proxiesError,isLoading:proxiesLoading,isFetched:proxiesFetched,}=useQuery({queryKey:["get-proxies"],queryFn:getWorkspaceProxies,})constproxyLatencies=useProxyLatency(proxiesResp)// This useEffect ensures the proxy to be used is updated whenever the state changes.// This includes proxies being loaded, latencies being calculated, and the user selecting a proxy.useEffect(()=>{setProxy(getPreferredProxy(proxiesResp?.regions??[],loadUserSelectedProxy(),proxyLatencies,),)},[proxiesResp,proxyLatencies])return(<ProxyContext.Providervalue={{getSavedProxy:()=>loadUserSelectedProxy(),proxyLatencies:proxyLatencies,proxy:experimentEnabled          ?proxy          :{// If the experiment is disabled, then call 'getPreferredProxy' with the regions from// the api call. The default behavior is to use the `primary` proxy.              ...getPreferredProxy(proxiesResp?.regions||[]),},proxies:proxiesResp?.regions,isLoading:proxiesLoading,isFetched:proxiesFetched,error:proxiesError,// These functions are exposed to allow the user to select a proxy.setProxy:(proxy:Region)=>{// Save to local storage to persist the user's preference across reloadssaveUserSelectedProxy(proxy)// Set the state for the current context.getPreferredProxy(proxiesResp?.regions??[],loadUserSelectedProxy())},clearProxy:()=>{// Clear the user's selection from local storage.clearUserSelectedProxy()// Set the state for the current context.getPreferredProxy(proxiesResp?.regions??[])},}}>{children}</ProxyContext.Provider>)}

Will take a look! The nice thing is if the tests pass, then it's all still good

We do not need to tackle this in your PR - can totally be future work, but just a heads up that we now have auseLocal hook that might be fun to add here some point down the line.