Sam Gleske
Sam Gleske
I posted in https://github.com/ray-project/ray/pull/40332 asking author if they mind if I pull in their C/C++ changes. If they don’t answer then I’ll update these files myself with my own take...
> @samrocketman not pushing but any ETA on when you think you'll open this up for review? I've been sick the past week so likely a week at least; I'm...
@anyscalesam worth calling out I've not operated Ray before. I've been making code changes based on core networking and programming concepts/experience. So when this is ready/out of draft any help...
I'll look at picking this up again. I made these changes in concept only (I don't currently operate ray but my environment does have ipv6 only clusters).
> ... can y'all reach out to me on ray.slack.com so I can invite you to the Ray Contributors sync to get some more traction on this? It says I...
I think it makes most sense to do this in two parts: 1. These supporting python changes which DRY up socket usage. The intent here is the code was reorganized...
> as the python codes relies on the c++ changes, will it be possible to submit and test the cpp changes first? My intent was to basically DRY up the...
Because I have approval to work on this during work hours I'll aim for full IPv6 support in this PR rather than breaking it up over multiple PRs. My primary...
@anyscalesam if you want to invite me to your ray slack instance you can find my email in my commit authorship of this PR
You need to configure the server (which is your ip range) followed by adding your client (with a single ip within the range i.e. /32).