Description
This is an upstream (Mutagen) issue. Not sure if it effects all Windows workspaces, or just the Windows Web RDP template I tried it against. Either way, we'll likely need to fix it on our fork.
Latest Mutagen release:
~/D/mutagen_darwin_arm64_v0.18.1 2 » ./mutagen sync create ~/Music/ "windows.coder:C:\Users\Default\Desktop"
Started Mutagen daemon in background (terminate with "mutagen daemon stop")
Connecting to agent (POSIX)...
Error: unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to handshake with agent process: unable to receive server magic number: EOF (error output: ^[[31;1m.mutagen/agents/0.18.1/mutagen-agent: ^[[31;1mThe term '.mutagen/agents/0.18.1/mutagen-agent' is not recognized as a name of a cmdlet, function, script file, or executable program.^[[0m\r
^[[31;1m^[[31;1mCheck the spelling of the name, or if a path was included, verify that the path is correct and try again.^[[0m)
Our fork:
/A/C/C/C/Resources » MUTAGEN_DATA_DIRECTORY="/Users/ethan/Library/Application Support/Coder Desktop/Mutagen" ./mutagen-darwin-arm64 sync create ~/Music/ "windows.coder:C:\Users\Default\Desktop"
Connecting to agent (POSIX)...
Error: unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to handshake with agent process: unable to receive server magic number: EOF (error output: ^[[31;1m~/.mutagen/agents/0.18.1/mutagen-agent: ^[[31;1mThe term '~/.mutagen/agents/0.18.1/mutagen-agent' is not recognized as a name of a cmdlet, function, script file, or executable program.^[[0m\r
^[[31;1m^[[31;1mCheck the spelling of the name, or if a path was included, verify that the path is correct and try again.^[[0m)
I discovered this in the macOS UI, where the user at least sees an error message in the meantime:
Metadata
Metadata
Assignees
Labels
No labels