Skip to content

Windows: short project name for the app's chat folders, and a path budget - #2082

Draft
Brian Krabach (bkrabach) wants to merge 5 commits into
mainfrom
windows-ootb/chat-folder-names
Draft

Brian Krabach (bkrabach) wants to merge 5 commits into
mainfrom
windows-ootb/chat-folder-names

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

Draft while the native Windows job is brought to green. The full description follows before this leaves draft.

Part of the Windows 11 out-of-the-box program (path length, parts A and C).

…dget

On Windows the app's own chat folders (<any>\chats\<UUID>\files) get a
21-character project name derived from the chat UUID. The shared CLI name of
such a folder repeats the installation path inside every session path, which
exceeds the Windows path limit when long paths are off (the default).

A chat that already has history under the CLI name keeps it; nothing is moved.
Folders a person chose and every other platform keep the CLI name.

Adds the path budget as a test, and a native Windows CI case that turns long
paths off on its runner and runs the real stores under the longest supported
installation folder.
…pt Python's own length refusal

The native canary showed that the runner honours LongPathsEnabled=0 for a new
process: 259 characters accepted, 260 refused in the same folder. Python's open
reports that refusal as errno 2 without a Windows code.
… open

A chat with history under the CLI name opens where it is. When both names hold
history for one chat ID (only after an update rollback) the chat still opens
under the short name and the other folder stays listed read-only.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants