Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Windows #101

Open
cschneid opened this issue Aug 1, 2018 · 3 comments
Open

Support Windows #101

cschneid opened this issue Aug 1, 2018 · 3 comments

Comments

@cschneid
Copy link
Member

@cschneid cschneid commented Aug 1, 2018

As of writing, we do not start on Microsoft Windows, for two reasons:

  1. On Windows os.O_NONBLOCK does not exist, causing an error when we open a socket
  2. The underlying binary Core Agent does not yet have a build for Windows.

See #100 for the issue about not starting on Windows until there is support.

@looser990
Copy link

@looser990 looser990 commented Apr 7, 2020

I suppose this one will not be supported any time soon? Also, there is no workaround around this? I'm a bit stucked on Windows ATM :/
Keep up the good work!

@adamchainz
Copy link
Contributor

@adamchainz adamchainz commented Apr 7, 2020

Hi @looser990

Thanks for asking. Unfortunately we aren't working on this right now.

One workaround would be to use Windows Subsystem for Linux. Are you deploying on Windows, or just developing?

Thanks,

Adam

@looser990
Copy link

@looser990 looser990 commented Apr 7, 2020

Only developing, so no biggy. Thanks for quick response and workaround, not sure if I'll have time to try it out but if I do I'll let you know if it works.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants