&`i]!VddlZddlZddlmZddlmZddlmZddlm Z m Z m Z ddl Z ddl mZddlmZe e jje jjfZde e eefd e eeffd ZeGd d ZeeGd dejZdS)N)deepcopy) dataclass) signature)DictListUnion)placement_group) DeveloperAPIbundlesreturnci}|D]8}|D]!\}}||d|z||<"9|S)zSum all resources in a list of resource bundles. Args: bundles: List of resource bundles. Returns: Dict containing all resources summed up. r)itemsget)r resourcesbundlekvs w/home/jaya/work/projects/VOICE-AGENT/VIET/agent-env/lib/python3.11/site-packages/ray/air/execution/resources/request.py _sum_bundlesrs\I33LLNN 3 3DAq$==A..2IaLL 3 cfeZdZdZ ddeeeeee ffdefdZ e dZ e e de fdZe e deeee ffd Ze deee ffd Ze e defd Zd Zd ZddZdZdZdZdefdZdS)ResourceRequestaRequest for resources. This class is used to define a resource request. A resource request comprises one or more bundles of resources and instructions on the scheduling behavior. The resource request can be submitted to a resource manager, which will schedule the resources. Depending on the resource backend, this may instruct Ray to scale up (autoscaling). Resource requests are compatible with the most fine-grained low-level resource backend, which are Ray placement groups. Args: bundles: A list of bundles which represent the resources requirements. E.g. ``[{"CPU": 1, "GPU": 1}]``. strategy: The scheduling strategy to acquire the bundles. - "PACK": Packs Bundles into as few nodes as possible. - "SPREAD": Places Bundles across distinct nodes as even as possible. - "STRICT_PACK": Packs Bundles into one node. The group is not allowed to span multiple nodes. - "STRICT_SPREAD": Packs Bundles across distinct nodes. *args: Passed to the call of ``placement_group()``, if applicable. **kwargs: Passed to the call of ``placement_group()``, if applicable. PACKr strategycP|stdd|D|_|jds8d|_|jd|jstdnd|_||_||_||_d|_d|_| dS)Nz6Cannot initialize a ResourceRequest with zero bundles.cJg|] }d|D!S)c@i|]\}}|dk |t|S)r)float).0rrs r z7ResourceRequest.__init__...Gs) > > >TQqAvvQavvvr)r)rrs r z,ResourceRequest.__init__..Fs<   CI > >V\\^^ > > >   rrTzOCannot initialize a ResourceRequest with an empty head and zero worker bundles.F) ValueError_bundles_head_bundle_is_emptypop _strategy_args_kwargs_hash_bound_bind)selfr rargskwargss r__init__zResourceRequest.__init__;s WUVV V  MT    }Q /)-D & M  a =  /  */D &!     rc|jS)zReturns True if head bundle is empty while child bundles need resources. This is considered an internal API within Tune. )r$r,s rhead_bundle_is_emptyz$ResourceRequest.head_bundle_is_emptybs ))rr cV|jrdn |jdddS)z.Returns the number of cpus in the head bundle.grCPU)r$r#rr1s r head_cpuszResourceRequest.head_cpusks.0VssdmA6F6J6J5RU6V6VVrc*t|jS)z'Returns a deep copy of resource bundles)rr#r1s rr zResourceRequest.bundlesqs &&&rc*t|jS)z3Returns a dict containing the sums of all resources)rr#r1s rrequired_resourcesz"ResourceRequest.required_resourceswsDM***rc|jS)zReturns the placement strategy)r&r1s rrzResourceRequest.strategy|s ~rctt} |j|j|jg|jRi|j|_dS#t$r}td|d}~wwxYw)aBind the args and kwargs to the `placement_group()` signature. We bind the args and kwargs, so we can compare equality of two resource requests. The main reason for this is that the `placement_group()` API can evolve independently from the ResourceRequest API (e.g. adding new arguments). Then, `ResourceRequest(bundles, strategy, arg=arg)` should be the same as `ResourceRequest(bundles, strategy, arg)`. ztInvalid definition for resource request. Please check that you passed valid arguments to the ResourceRequest object.N) rr bindr#r&r'r(r* Exception RuntimeError)r,sigexcs rr+zResourceRequest._binds(( "#( t~04 >BlDKKK      s+A A" AA"cBt|jji|jjSN)r r*r-r.r1s rto_placement_groupz"ResourceRequest.to_placement_groups 0GDK4FGGGrotherclt|to|j|jko|j|jkSrA) isinstancerr*r2)r,rCs r__eq__zResourceRequest.__eq__s: uo . . H u|+ H)U-GG rc|jsAttj|jj|jjdddd|_|jS)N)r-r.Tr) sort_keysindent ensure_ascii)r)hashjsondumpsr*r-r.r1s r__hash__zResourceRequest.__hash__sYz  ![-9KLL"!% DJzrc|j}|dd|dd|S)Nr)r*)__dict__copyr%r,states r __getstate__zResourceRequest.__getstate__sB ""$$ '4    (D!!! rc~|j|d|_d|_|dSrA)rPupdater)r*r+rRs r __setstate__zResourceRequest.__setstate__s7 U###   rc(d|jd|jdS)Nz)r*r2r1s r__repr__zResourceRequest.__repr__s5 B  B B$($= B B B rN)r)rCr)__name__ __module__ __qualname____doc__rrstrrintrr/propertyr2r r5r r8rr+rBrFrNrTrWrYrrrrs<%%d3c5j 1123%%%%%N**X*W5WWW\XW'd3:./'''\X'+De$4+++X+#\X*HHH          #      rrczeZdZUdZeed<deedeeefdZ dede e e fde defd Zd S) AcquiredResourcesaBase class for resources that have been acquired. Acquired resources can be associated to Ray objects, which can then be scheduled using these resources. Internally this can point e.g. to a placement group, a placement group bundle index, or just raw resources. The main API is the `annotate_remote_entities` method. This will associate remote Ray objects (tasks and actors) with the acquired resources by setting the Ray remote options to use the acquired resources. resource_requestentitiesr c|jj}t|t|jjz}t||kr#t dt|d|dg}|jjr;|||did|dd}tt||D]3\}\}}|||||4|S)aAReturn remote ray entities (tasks/actors) to use the acquired resources. The first entity will be associated with the first bundle, the second entity will be associated with the second bundle, etc. Args: entities: Remote Ray entities to annotate with the acquired resources. z%The number of callables to annotate (z1) cannot exceed the number of available bundles (z).r) bundle_indexN) rdr lenr_r2r=append_annotate_remote_entity enumeratezip)r,rer num_bundles annotatedientityrs rannotate_remote_entitiesz*AcquiredResources.annotate_remote_entitiessC'/'llS)>)S%T%TT x==; & &KH KK;FKKK    5 $   ,,Xa["1,MM     |H#,S7-C-C#D#D   A   ,,VV!,LL    rrqrrgctrA)NotImplementedError)r,rqrrgs rrkz)AcquiredResources._annotate_remote_entitys "!rN)rZr[r\r]r__annotations__rRemoteRayEntityrrrrr^rr_rkrarrrcrcs  &%%%'_-' eO$ %''''R"%"/3CJ/?"OR" """"""rrc)abcrLrQr dataclassesrinspectrtypingrrrrayray.utilr ray.util.annotationsr remote_functionRemoteFunctionactor ActorClassrvr^rrrABCrcrarrrst !!!!!!$$$$$$$$$$ $$$$$$------+:CI