agent connection timings rendering as negative values when agent cannot connect #15432
Comments
|
Related issue: https://coder.zendesk.com/agent/tickets/3527 |
|
@dannykopping instead of returning a golang zero value, would be possible to return null instead? |
|
Are you asking if it's possible technically, or whether I can make that change? |
|
Both. If a date is "not defined", as consumer, I would expect it to be null instead of having a "zero value" related to a very specific language. Wdyt? |
|
I'm pretty swamped with other work so I won't have time to look at this soon, but yes I agree - this should've never sent back a zero value for the date. |
|
@BrunoQuaresma on the UI side, can we assume that a zero value for this value is effectively null? If those times are golang durations, they're nanoseconds and zero would be impossible as a real value. |
I recently played with workspaces build and in some situations had workspaces struggling to be healthy.
While watching at the build timeline for this workspace - the
connectstep for the agent is displaying a weird value.Looking at the JSON for the endpoint, the
ended_atfield returned seems to be a Golang zero value.{ "started_at": "2024-11-07T17:52:51.485204Z", "ended_at": "0001-01-01T00:00:00Z", "stage": "connect", "workspace_agent_id": "67e37a9d-ccac-497e-8f48-4093bcc4f3e7", "workspace_agent_name": "main" }An easy way to reproduce is to create or modify an existing template and change the
hostvalue in theworkspace- which will result in the agent being impossible to contact.Overall view of the workspace
The text was updated successfully, but these errors were encountered: