VNC currently routes to UnsupportedSessionBackend with an explicit not-implemented message. This milestone was deferred; reopening as a tracked issue so it isn't lost.
Planned scope (per docs/PROGRESS.md Milestone 6):
Replace the unsupported VNC path with a complete VNC implementation
Deliver usable in-app VNC session behavior aligned to SSH/RDP UX
Extend profile/session connect options needed by VNC
Standardize event log and error mapping behavior with SSH/RDP
VNC currently routes to `UnsupportedSessionBackend` with an explicit not-implemented message. This milestone was deferred; reopening as a tracked issue so it isn't lost.
Planned scope (per docs/PROGRESS.md Milestone 6):
- Replace the unsupported VNC path with a complete VNC implementation
- Deliver usable in-app VNC session behavior aligned to SSH/RDP UX
- Implement VNC connect/disconnect/reconnect lifecycle handling
- Extend profile/session connect options needed by VNC
- Standardize event log and error mapping behavior with SSH/RDP
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
VNC currently routes to
UnsupportedSessionBackendwith an explicit not-implemented message. This milestone was deferred; reopening as a tracked issue so it isn't lost.Planned scope (per docs/PROGRESS.md Milestone 6):