-
-
Notifications
You must be signed in to change notification settings - Fork 922
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
Socket::Constants incorrect on Windows #1509
Comments
jRuby was not returning the correct socket hint values see jruby/jruby#1509 Clean up TLS memory in TCP Adjust some specs so they pass on windows bump version
@ahorek I merged that I and I guess we will need to run a script to populate for next jnr-constant release but I see we hard-coded numbers in that commit above. Maybe we can get more updated for AF_INET and AF_INET6 are generated? Or is that not in jnr-constant? |
@enebo thanks after that we have to run the generation script for all platforms and commit generated files separately. Sounds good? |
cotag/libuv@22e0ed6 no, this one isn't in jnr-constant repository. It was a workaround for https://github.com/cotag/libuv jnr/jnr-constants#31 will fix it properly |
I've merged all mentioned PRs for jnr-constants. There's no changes when regenerating for MacOS. |
there should be changes for all supported platforms including macos. I ran these commands on linux and windows
but something went wrong, do you have a tip how to fix these failures?
|
@headius it's ready to review. I fixed tests and added constants for freebsd, windows, linux and solaris, but I don't have any macos, aix and openbsd running. |
Hmm... I ran those commands too and didn't get anything new. I'll try again. |
Closing the loop... jnr/jnr-constants#41 and related PRs were needed to fix a bunch of decay in the generation of jnr-constants. Those are now merged, @ahorek is regenerating for their available platforms, and we should be good to go with a jnr-constants release for 9.2.1. |
Looks like some failures in Errno we'll have to look into. |
According to MSDN values should be
The text was updated successfully, but these errors were encountered: