-
Notifications
You must be signed in to change notification settings - Fork 886
Some metadata disappears from the UI for a long time, repeatedly #8577
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
Comments
I am seeing the same behavior too. |
One thing to look for is what data the web socket is sending. Sometimes I have seen the server sending null values making the loading state to be visible. I also noticed this happens during Coder deployments and when we have some instability(in the last two weeks I have been facing some timeouts when using yarn dev pointing to dev.coder.com, I thought it would be because of Coder deployments but they are very frequent). We could make the FE just ignore null values but I would rather do the fix on the BE so other clients would not have to work around this. |
I have reproduced the issue on a deployment that follows the dev.coder.com version. |
I believe this is the fix for #8577. When looking at the websocket, metadata keys go over 2 minutes without updating, even when their interval is much lower. This fixes `reportMetadataLoop` to run every second and properly calculate the interval. A previous refactor set it to tick each minute instead of the previous behavior of each second.
fixed by #8614 |
I don't know what's the cause, but using the Coder on Coder template on dev.coder.com, I'm seeing metadata appears for a short while, only to disappear again. This happens repeatedly.
Meanwhile, the VSCode extension is showing the values correctly.
Video:
Screen.Recording.2023-07-18.at.17.07.16.mov
Metadata appear at 0:58 and 3:58, so it seems to be on some interval. There might've been a redeploy/reconnect of dev.coder.com too somewhere around the 3-minute mark.
The text was updated successfully, but these errors were encountered: