See below seems like there is an outage or a bug.
I hard reset cache and logged out and in and still same issue.
Status page on Fly.io says everything is up.
Anyone else having this issue?
app-e691e3c85acacc74ec08ab94121b8c93.js?vsn=d:82 Lit has been loaded from a bundle that combines all core features into a single file. To reduce transfer size and parsing cost, consider using the `lit` npm package directly in your project.
(anonymous) @ app-e691e3c85acacc74ec08ab94121b8c93.js?vsn=d:82
/i/ide/?workspace=/root/workspaces/fly-lqjcim.code-workspace:1
Failed to load resource: the server responded with a status of 500 ()
_e96e9bea.js:19 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
at d (_e96e9bea.js:19:19171)
_e96e9bea.js:19 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
at d (_e96e9bea.js:19:19171)
_e96e9bea.js:19 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
at d (_e96e9bea.js:19:19171)
_e96e9bea.js:19 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
at d (_e96e9bea.js:19:19171)
app-e691e3c85acacc74ec08ab94121b8c93.js?vsn=d:73 Uncaught (in promise) TypeError: s is not a function
at app-e691e3c85acacc74ec08ab94121b8c93.js?vsn=d:73:35894
Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.
ide/:1
Failed to load resource: the server responded with a status of 500 ()