You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Creating workspaces hang when using uppercase workspace name #1471
I see. Do you have any logs related to this just to help me understand what's happening better on your end? And you said this only happens on a workspace with the uppercase name?
Devsy v1.24.0, Fedora 44, GNOME 50. No logs since the container doesn't even build or shows logs at all (Waiting for input on log tab).
Then, it get stuck:
I change the name to lowercase...
And it works!
My guess is that naming becomes invalid since it's not domain mapeable, but be my guest. Surely it won't work if I had something like special characters or emojis (didn't test this)
I'm still working on some user interface improvements, but could I get you to go to the settings panel and on the general section for desktop application logging and CLI capture logging. Can you set both of those values to debug?
Activity
DarkGhostHunter commentedon Oct 12, 2026
I just deleted everything and tried again, downloaded the release from GitHub v1.23.2, and it worked.
DarkGhostHunter commentedon Oct 18, 2026
Seems that there is a problem with the workspace naming. The moment I try something uppercase, the "Launching workspace" hangs.
[-][Bug]: Creating workspaces hang[/-][+][Bug]: Creating workspaces hang when using uppercase workspace name[/+]skevetter commentedon Oct 18, 2026
I see. Do you have any logs related to this just to help me understand what's happening better on your end? And you said this only happens on a workspace with the uppercase name?
DarkGhostHunter commentedon Oct 19, 2026
Devsy v1.24.0, Fedora 44, GNOME 50. No logs since the container doesn't even build or shows logs at all (Waiting for input on log tab).
Then, it get stuck:
I change the name to lowercase...
And it works!
My guess is that naming becomes invalid since it's not domain mapeable, but be my guest. Surely it won't work if I had something like special characters or emojis (didn't test this)
skevetter commentedon Oct 19, 2026
I'm still working on some user interface improvements, but could I get you to go to the settings panel and on the general section for desktop application logging and CLI capture logging. Can you set both of those values to debug?
DarkGhostHunter commentedon Oct 19, 2026
Yeah, but were are the logs?
DarkGhostHunter commentedon Oct 19, 2026
BTW, doing the same, show the logs
resolving workspace with ide="none" launch="auto"and stays there.skevetter commentedon Oct 19, 2026
They should show right below the launch activity in the launching workspace.
skevetter commentedon Oct 19, 2026
I'm going to try to reproduce on my end, but I need to set up Podman.
rkl110 commentedon Oct 21, 2026
Same problem here on macOS. It looks like the input validation for the name isn’t working. Adding a “.” to the name also prevents it from starting.