-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCloud auth expiration doesn't disconnect cleanly #1098
Comments
@flippingbits since we also see I'm surprised we don't get any other websocket events aside from |
Thanks for reporting it and looping me in, @shouples! I don't think #855 would handle this issue, as the From reading the logs, the sidecar seems to report that the CCloud control plane token is invalid after consulting the CCloud API: It looks like the absolute lifetime of the refresh token ended at Unfortunately, the sidecar doesn't report a non-transient error in this case, which would let the VS Code extension prompt the user to re-authenticate, but assumes that the VS Code extension has noted the I feel we should fix this on the sidecar side and let it reset the CCloud connection (and set its status to the initial |
@flippingbits thanks for the info here! Currently the extension blocks any CCloud-related requests via its middleware when we see the And yep, we should be floating CCloud auth expiration warning notifications as soon as the session has <1hr before the 8hr window. |
Seen after hitting the 8-hour session expiration, where it looks like we only got an
INVALID_TOKEN
status:The text was updated successfully, but these errors were encountered: