yetone
0361189f9e
test: every package's tests pass on Windows, and none writes outside its sandbox (the user: 把 Windows 上那几个失败的测试修掉) — on a Windows box the suite failed in most packages, and the root package hung for 25 minutes. Tests set HOME, which os.UserHomeDir ignores on Windows (it reads USERPROFILE), so they read and wrote the runner's own home; each now sets USERPROFILE beside HOME, and Devin's, Goose's, Crush's and Claude Desktop's tests set APPDATA/LOCALAPPDATA, where those keep their files there. said() read the command's output only once it returned, and a pipe holds a few KB on Windows, so magpie model --help blocked forever; it reads while the command writes. Unix permission bits (the gateway key store's 0600 too), exec bits and symlinks Windows lacks are checked only off Windows; TOML strings hold Windows paths as literal strings, JSON as marshalled ones; a URL's path is compared as one. The provider and usage packages run in a home of their own (TestMain, as the gateway's already does), since a CLI's identity kept by a refresh still going when its test ended landed in the runner's ~/.config/magpie — and on a Mac in the user's own. Two product fixes came out of it: imagemcp took a file:///C:/… root or image for the path /C:/…, which doesn't exist on Windows, and now makes a Windows path of it (a host for a UNC share); and session discovery could keep a new Cowork session hidden on Linux, where a folder's mtime is a kernel tick and its size doesn't change, so an entry added within the tick of the last listing left both as they were — a listing made within 2s of its folder's last change is read again, as git does for racy files. TestFilePath and TestRacyDirectoryListedAgain fail without the change. On Windows 11 every package passes (32 of 32) and a run of each package in a fresh home leaves nothing in home, APPDATA or LOCALAPPDATA; on Linux (WSL) and macOS go test -tags nogui ./... passes. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build pass.
2026-10-01 23:15:07 +08:00
..
test: every package's tests pass on Windows, and none writes outside its sandbox (the user: 把 Windows 上那几个失败的测试修掉) — on a Windows box the suite failed in most packages, and the root package hung for 25 minutes. Tests set HOME, which os.UserHomeDir ignores on Windows (it reads USERPROFILE), so they read and wrote the runner's own home; each now sets USERPROFILE beside HOME, and Devin's, Goose's, Crush's and Claude Desktop's tests set APPDATA/LOCALAPPDATA, where those keep their files there. said() read the command's output only once it returned, and a pipe holds a few KB on Windows, so magpie model --help blocked forever; it reads while the command writes. Unix permission bits (the gateway key store's 0600 too), exec bits and symlinks Windows lacks are checked only off Windows; TOML strings hold Windows paths as literal strings, JSON as marshalled ones; a URL's path is compared as one. The provider and usage packages run in a home of their own (TestMain, as the gateway's already does), since a CLI's identity kept by a refresh still going when its test ended landed in the runner's ~/.config/magpie — and on a Mac in the user's own. Two product fixes came out of it: imagemcp took a file:///C:/… root or image for the path /C:/…, which doesn't exist on Windows, and now makes a Windows path of it (a host for a UNC share); and session discovery could keep a new Cowork session hidden on Linux, where a folder's mtime is a kernel tick and its size doesn't change, so an entry added within the tick of the last listing left both as they were — a listing made within 2s of its folder's last change is read again, as git does for racy files. TestFilePath and TestRacyDirectoryListedAgain fail without the change. On Windows 11 every package passes (32 of 32) and a run of each package in a fresh home leaves nothing in home, APPDATA or LOCALAPPDATA; on Linux (WSL) and macOS go test -tags nogui ./... passes. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build pass.
2026-10-01 23:15:07 +08:00
autostart: a magpie opened at login comes back from "update and restart" on the Mac (悠悠哥 on Discord: 更新后开机自启动没了) — open at login was never lost: the Mac's launch agent runs magpie as a launchd job, and launchd ends whatever a job started once the job exits, so the shell update.Relaunch leaves to open the new version was killed as magpie quit and magpie never came back. The launch agent now carries AbandonProcessGroup, and the desktop app rewrites one an older magpie wrote in the current form at start, keeping the program path it names; with none it stays off, and a launch agent magpie didn't write is left alone. Two throwaway launchd jobs showed children, detached ones too, killed on the job's exit without the key and living with it. TestLaunchAgentLetsTheRelaunchLive and TestRefreshOlderLaunchAgent fail without the change. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build, go test -tags nogui ./... pass.
2026-10-01 19:38:36 +08:00
autostart: a magpie opened at login comes back from "update and restart" on the Mac (悠悠哥 on Discord: 更新后开机自启动没了) — open at login was never lost: the Mac's launch agent runs magpie as a launchd job, and launchd ends whatever a job started once the job exits, so the shell update.Relaunch leaves to open the new version was killed as magpie quit and magpie never came back. The launch agent now carries AbandonProcessGroup, and the desktop app rewrites one an older magpie wrote in the current form at start, keeping the program path it names; with none it stays off, and a launch agent magpie didn't write is left alone. Two throwaway launchd jobs showed children, detached ones too, killed on the job's exit without the key and living with it. TestLaunchAgentLetsTheRelaunchLive and TestRefreshOlderLaunchAgent fail without the change. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build, go test -tags nogui ./... pass.
2026-10-01 19:38:36 +08:00
test: every package's tests pass on Windows, and none writes outside its sandbox (the user: 把 Windows 上那几个失败的测试修掉) — on a Windows box the suite failed in most packages, and the root package hung for 25 minutes. Tests set HOME, which os.UserHomeDir ignores on Windows (it reads USERPROFILE), so they read and wrote the runner's own home; each now sets USERPROFILE beside HOME, and Devin's, Goose's, Crush's and Claude Desktop's tests set APPDATA/LOCALAPPDATA, where those keep their files there. said() read the command's output only once it returned, and a pipe holds a few KB on Windows, so magpie model --help blocked forever; it reads while the command writes. Unix permission bits (the gateway key store's 0600 too), exec bits and symlinks Windows lacks are checked only off Windows; TOML strings hold Windows paths as literal strings, JSON as marshalled ones; a URL's path is compared as one. The provider and usage packages run in a home of their own (TestMain, as the gateway's already does), since a CLI's identity kept by a refresh still going when its test ended landed in the runner's ~/.config/magpie — and on a Mac in the user's own. Two product fixes came out of it: imagemcp took a file:///C:/… root or image for the path /C:/…, which doesn't exist on Windows, and now makes a Windows path of it (a host for a UNC share); and session discovery could keep a new Cowork session hidden on Linux, where a folder's mtime is a kernel tick and its size doesn't change, so an entry added within the tick of the last listing left both as they were — a listing made within 2s of its folder's last change is read again, as git does for racy files. TestFilePath and TestRacyDirectoryListedAgain fail without the change. On Windows 11 every package passes (32 of 32) and a run of each package in a fresh home leaves nothing in home, APPDATA or LOCALAPPDATA; on Linux (WSL) and macOS go test -tags nogui ./... passes. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build pass.
2026-10-01 23:15:07 +08:00
autostart: a magpie opened at login comes back from "update and restart" on the Mac (悠悠哥 on Discord: 更新后开机自启动没了) — open at login was never lost: the Mac's launch agent runs magpie as a launchd job, and launchd ends whatever a job started once the job exits, so the shell update.Relaunch leaves to open the new version was killed as magpie quit and magpie never came back. The launch agent now carries AbandonProcessGroup, and the desktop app rewrites one an older magpie wrote in the current form at start, keeping the program path it names; with none it stays off, and a launch agent magpie didn't write is left alone. Two throwaway launchd jobs showed children, detached ones too, killed on the job's exit without the key and living with it. TestLaunchAgentLetsTheRelaunchLive and TestRefreshOlderLaunchAgent fail without the change. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build, go test -tags nogui ./... pass.
2026-10-01 19:38:36 +08:00
autostart: a magpie opened at login comes back from "update and restart" on the Mac (悠悠哥 on Discord: 更新后开机自启动没了) — open at login was never lost: the Mac's launch agent runs magpie as a launchd job, and launchd ends whatever a job started once the job exits, so the shell update.Relaunch leaves to open the new version was killed as magpie quit and magpie never came back. The launch agent now carries AbandonProcessGroup, and the desktop app rewrites one an older magpie wrote in the current form at start, keeping the program path it names; with none it stays off, and a launch agent magpie didn't write is left alone. Two throwaway launchd jobs showed children, detached ones too, killed on the job's exit without the key and living with it. TestLaunchAgentLetsTheRelaunchLive and TestRefreshOlderLaunchAgent fail without the change. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build, go test -tags nogui ./... pass.
2026-10-01 19:38:36 +08:00