[Job] [python 3.11] Fixes agent info container type

[frazierprime]

Why are these changes needed?

Breaking change introduced in python 3.11 to the random package https://docs.python.org/3.11/library/random.html#random.sample

Sample throws a type error when passed a non-sequence object (in this case, a set).

This PR changes the set type to sorted, as per the error message:
TypeError: Population must be a sequence. For dicts or sets, use sorted(d).

Related issue number

Fixes #36578

Checks - TODO

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR. - See comment in issue. Can't build project dependencies in python 3.11
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests

[frazierprime]

Not sure this is related to my change, but here's the output from the broken tests.

E       2023-06-21 11:45:27,452	INFO tune.py:666 -- [output] This will use the new output engine with verbosity 2. To disable the new output and use the legacy output engine, set the environment variable RAY_AIR_NEW_OUTPUT=0. For more information, please see https://docs.ray.io/en/master/ray-air/experimental-features.html
--
  | E       Traceback (most recent call last):
  | E         File "ray_tune_basic.py", line 14, in <module>
  | E           tune.run(objective)
  | E         File "/ray/python/ray/tune/tune.py", line 965, in run
  | E           callbacks = _create_default_callbacks(
  | E         File "/ray/python/ray/tune/utils/callback.py", line 141, in _create_default_callbacks
  | E           callbacks.append(TBXLoggerCallback())
  | E         File "/ray/python/ray/tune/logger/tensorboardx.py", line 173, in __init__
  | E           from tensorboardX import SummaryWriter
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/__init__.py", line 5, in <module>
  | E           from .torchvis import TorchVis
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/torchvis.py", line 11, in <module>
  | E           from .writer import SummaryWriter
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/writer.py", line 17, in <module>
  | E           from .comet_utils import CometLogger
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/comet_utils.py", line 6, in <module>
  | E           from .summary import _clean_tag
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/summary.py", line 13, in <module>
  | E           from .proto.summary_pb2 import Summary
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/proto/summary_pb2.py", line 16, in <module>
  | E           from tensorboardX.proto import tensor_pb2 as tensorboardX_dot_proto_dot_tensor__pb2
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/proto/tensor_pb2.py", line 16, in <module>
  | E           from tensorboardX.proto import resource_handle_pb2 as tensorboardX_dot_proto_dot_resource__handle__pb2
  | E         File "/opt/miniconda/lib/python3.8/site-packages/tensorboardX/proto/resource_handle_pb2.py", line 36, in <module>
  | E           _descriptor.FieldDescriptor(
  | E         File "/opt/miniconda/lib/python3.8/site-packages/google/protobuf/descriptor.py", line 561, in __new__
  | E           _message.Message._CheckCalledFromGeneratedFile()
  | E       TypeError: Descriptors cannot not be created directly.
  | E       If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
  | E       If you cannot immediately regenerate your protos, some other possible workarounds are:
  | E        1. Downgrade the protobuf package to 3.20.x or lower.
  | E        2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

[architkulkarni]

The test failures are unrelated and flaky according to https://flaky-tests.ray.io/

[architkulkarni]

Looks good to me, thanks for the fix. @rickyyx I guess at some point in the Python 3.11 process, all existing Ray tests will be run with Python 3.11, but is there some CI job where we should add jobs tests today?

[rickyyx]

Looks good to me, thanks for the fix. @rickyyx I guess at some point in the Python 3.11 process, all existing Ray tests will be run with Python 3.11, but is there some CI job where we should add jobs tests today?

I think right now - minimal test is the only test group we run py > 3.8

We should run some non-minimal tests on py >3.8 as well. I believe job is not part of minimal?

[architkulkarni]

Right, jobs requires the dashboard server, so I think it's not part of minimal.