Autostop keeps refreshing even though workspace is not used

[GilQedma]

Hey, using coder v2.7.2+a82a8c7 on EKS.

My workspace keeps bumping autostop (it always stays around 57-60 minutes to shutdown)

1. I checked the admin toolbar, to consult the "Active Connections" - it says zero connections.
2. I talked with the owner of the Workspace, and it is indeed was not used during these times (when used, he usually uses VSCode extension)

What could be the cause for that?

[stirby]

I'm going to work on reproducing this. What is the Autostop configuration on the workspace?

[GilQedma]

Thanks! Here it is -

[johnstcn]

I noticed this just now on my own workspace. I have autostop enabled with an aggressive TTL of 1 hour. From checking coderd logs matching msg:"read stats report" workspace_id:<workspace_id> I noticed that opening or loading the workspace page appears to trigger something that causes workspace stats to be posted with a non-zero connection count, which triggers ActivityBumpWorkspace(). I'm not sure exactly what is causing it yet, my best guess so far is the "Open Ports" indicator but it's not a given just yet.

Edit: note this is on latest main and not 2.7.2; so it's less likely that this that paritcular item is related.

[johnstcn]

@GilQedma is it possible the developer had done one of the following:

• Left a port-forward open to the workspace
• Left a persistent connection open to an application running inside the workspace besides VSCode?

Both of these actions will be counted as 'active usage' and will trigger the activity bump, but won't show up in the admin toolbar.

[GilQedma]

@johnstcn could certainly be! I'll check it out.
The developer uses VSCode terminal, and also tmux, so could be.

[GilQedma]

I talked to the developer @johnstcn, he isn't aware of any port-forward left open, or a persistent connection as such.
This actually happened while he wasn't working on his laptop.

However, he said that the auto-refresh issue didn't happen to him for some time now (still v2.7.2)... so perhaps we should put this on hold until it happens again. Thanks for the help!