What
Run a real plugin through the plugin manager on Windows and confirm the full lifecycle works: discovery, launch with --address/--network, gRPC handshake over the socket, request flow, shutdown, and socket cleanup.
Why
#221 removed the TCP transport that Windows previously used, leaving Unix domain sockets as the only plugin transport. Windows 10 1803+ supports AF_UNIX and a Go net.Listen("unix", ...) round-trip works on a Windows host, but no plugin has been exercised end to end there. This has to be confirmed before Windows builds are published again.
Things to check
- Socket paths under
os.TempDir() stay within the Windows sun_path limit.
- Stale socket files are removed on restart (Windows will not let you bind over an existing one).
- The plugin SDK side dials a Unix socket correctly on Windows.
- Decide whether TCP needs to come back as a fallback, or whether Unix sockets are the supported transport on all platforms.
How to test
Manual run of a sample plugin on Windows, ideally captured as an integration test that can run on the Windows CI runner.
What
Run a real plugin through the plugin manager on Windows and confirm the full lifecycle works: discovery, launch with
--address/--network, gRPC handshake over the socket, request flow, shutdown, and socket cleanup.Why
#221 removed the TCP transport that Windows previously used, leaving Unix domain sockets as the only plugin transport. Windows 10 1803+ supports
AF_UNIXand a Gonet.Listen("unix", ...)round-trip works on a Windows host, but no plugin has been exercised end to end there. This has to be confirmed before Windows builds are published again.Things to check
os.TempDir()stay within the Windowssun_pathlimit.How to test
Manual run of a sample plugin on Windows, ideally captured as an integration test that can run on the Windows CI runner.