Skip to content

Glimmervoid v0.42.1

Choose a tag to compare

@johncwaters johncwaters released this 20 Oct 21:48
· 2412 commits to main since this release
v0.42.1
ccaa49e

Changed

  • The needs-you box at the top of the rail is easier to read: instead of one purple "1 NEEDS YOU, 1 FAILED, 1 FINISHED" line that wrapped in a narrow rail, it now shows one chip per kind with the same icon and color as the session rows (needs input, failed, finished) and its count, and hovering a chip names it. The box is taller, its border takes the color of the most urgent kind present, and the Cmd+J (Alt+J off a Mac) keys no longer stack on top of each other. ALL CLEAR shows in a plain box when nothing needs you. The phone Board shows the same chips beside its Next button.

Fixed

  • A remote session card says why its connection ended: when a remote session's connection to its Coder workspace ended, the card showed failed with no reason. Now it names the cause: the workspace stopped (by its idle stop or its stop-after limit), was deleted, failed, or the connection was lost, and what Restart will do about it. Restart on a workspace Coder reports as failed now gets a fresh workspace too.
  • Restarting a failed remote session gets it a fresh workspace: a remote session whose Coder workspace failed to come up, or was deleted outside Glimmervoid, used to fail again with the same reason on every restart, so the only way out was to close it and start a new one. Now Restart provisions a fresh workspace for that session and starts it there, keeping its branch name. The old workspace, if Coder still lists it, is stopped and later deleted like any other workspace this host no longer uses. If the environment is already at its live workspace limit, Restart says so instead.
  • Removing a remote session deletes its Coder workspace: removing a remote session used to leave its workspace running and billing. Now Glimmervoid checks the workspace's checkout first. If nothing is uncommitted, stashed or unpushed, the session is stopped and the workspace is deleted with it. If there is unsaved work, or the check cannot run because the workspace is stopped or unreachable, the removal is refused with the branch and workspace named, and the dialog offers Discard remote work to delete it anyway. Removing a session while its workspace is still being created waits for that first.