Open artem-shelkovnikov opened 1 year ago
@artem-shelkovnikov do you already have an idea of the impact? Is it just a matter of adding some conditions and OS specific signals? If there is a simple way to fix it, I would suggest to just do it. If now, we may want to remove Windows from the support matrix and work on it in the next release
@jmb2154 what's the use-case for you for running connectors on Windows?
We normally recommend running them from Docker on Windows.
@artem-shelkovnikov Docker only runs on Windows under 3 conditions:
@jmb2154 I see.
Also a question - do these enterprise customers work with only Windows servers? Spinning a small unix machine should be relatively easy, but I could see people on Microsoft. stack having only Windows machines in their data centers.
@artem-shelkovnikov They only have Windows servers.
Bug Description
Due to our signal handling, connector service is unable to start on Windows without usage of Unix Subsystem. It happens because our signal handling (Ctrl+C and killing with
kill
command) is unix-specific.We need to add support for windows-specific signals to the framework.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Service just runs
Screenshots