§ `ƒij&ãó—ddlZddlZddlmZddlmZmZmZddlm Z m Z m Z ddl m Z mZmZmZddlmZgd¢Zed¬ ¦«Gd „d ¦«¦«ZGd „d ej¦«ZGd„dej¦«ZdS)éN)Ú dataclass)ÚAnyÚOptionalÚUnion)ÚMetadataÚ MetadataIndexÚ StorageMeta)ÚLoadPlanÚ LoadPlannerÚSavePlanÚ SavePlanner)ÚFuture)Ú WriteResultÚ StorageWriterÚ StorageReaderT)Úfrozencó.—eZdZUeed<eed<eed<dS)rÚindexÚ size_in_bytesÚ storage_dataN)Ú__name__Ú __module__Ú __qualname__rÚ__annotations__Úintr©óúx/home/jaya/work/projects/VOICE-AGENT/VIET/agent-env/lib/python3.11/site-packages/torch/distributed/checkpoint/storage.pyrrs6€€€€€€à ÐÐÑàÐÐÑØÐÐÑÐÐrrc óð—eZdZdZejddeeej dfddfd„¦«Z ejde de de ddfd „¦«Z ejd edefd „¦«Zejd eedeefd „¦«Zejd ededeeefd„¦«Zejdedeeeddfd„¦«Zeejdeeej fde fd„¦«¦«Zdeefd„ZdS)ra8 Interface used by ``save_state_dict`` to write to storage. One StorageWriter instance acts as both the coordinator and the follower in a distributed checkpoint. As part of initialization, each instance is told its role. A subclass should expect the following sequence of calls. 0) (all ranks) set checkpoint_id if users pass a valid checkpoint_id. 1) (all ranks) set_up_storage_writer() 2) (all ranks) prepare_local_plan() 3) (coordinator) prepare_global_plan() 4) (all ranks) write_data() 5) (coordinator) finish() NÚ checkpoint_idÚreturncó—dS)a© Calls to indicates a brand new checkpoint write is going to happen. A checkpoint_id may be present if users set the checkpoint_id for this checkpoint write. The meaning of the checkpiont_id is storage-dependent. It can be a path to a folder/file or a key for a key-value storage. Args: checkpoint_id (Union[str, os.PathLike, None]): The ID of this checkpoint instance. The meaning of the checkpoint_id depends on the storage. It can be a path to a folder or to a file. It can also be a key if the storage is a key-value store. (Default: ``None``) Nr©Úselfr s rÚresetzStorageWriter.reset-ó €ð ˆrÚis_coordinatorÚargsÚkwargscó—dS)z± Initialize this instance. Args: is_coordinator (bool): Whether this instance is responsible for coordinating the checkpoint. Nr)r$r'r(r)s rÚset_up_storage_writerz#StorageWriter.set_up_storage_writer?ó€€€rÚplancó—dS)a‰ Perform storage-specific local planning. While this method can produce a completely different plan, the recommended way is to store storage specific data in SavePlan::storage_data. Args: plan (SavePlan): The local plan from the ``SavePlanner`` in use. Returns: A transformed ``SavePlan`` after storage local planning Nr©r$r-s rÚprepare_local_planz StorageWriter.prepare_local_planKr,rÚplanscó—dS)aÌ Perform centralized planning of storage. This method is only called on the coordinator instance. While this method can produce a completely different plan, the preferred way is to store storage specific data in SavePlan::storage_data. Args: plans: A list of ``SavePlan`` instances, one for each rank. Returns: A list of transformed ``SavePlan`` after storage global planning Nr©r$r1s rÚprepare_global_planz!StorageWriter.prepare_global_planZr,rÚplannercó—dS)a Write all items from ``plan`` using ``planner`` to resolve the data. A subclass should call ``SavePlanner::resolve_data`` on each item from the plan to get access to the underlying object to write. Subclasses should lazily call `resolve_data` as it can allocate memory. In case of tensors, make following assumptions: - They might be on any device, including not matching the one on ``WriteItem::tensor_data`` - They might be views or not contiguous. Only the projection needs to be saved. Args: plan (SavePlan): The save plan to execute. planner (SavePlanner): Planner object to be used to resolve items to data. Returns: A future that completes to a list of WriteResult Nr©r$r-r5s rÚ write_datazStorageWriter.write_datakr,rÚmetadataÚresultscó—dS)a½ Write the metadata and marks the current checkpoint as successful. The actual format/schema used for serializing `metadata` is an implementation detail. The only requirement is that it's recoverable in to the same object graph. Args: metadata (Metadata): metadata for the new checkpoint results: A list of WriteResults from all ranks. Returns: None Nr)r$r9r:s rÚfinishzStorageWriter.finishƒr,rcó—dS©zŒ Check if the given checkpoint_id is supported by the storage. This allow us to enable automatic storage selection. Nr©Úclsr s rÚvalidate_checkpoint_idz$StorageWriter.validate_checkpoint_id”ó €ð ˆrcó—dS)a= Return the storage-specific metadata. This is used to store additional information in a checkpoint that can be useful for providing request-level observability. StorageMeta is passed to the ``SavePlanner`` during save calls. Returns None by default. TODO: provide an example Nr)r$s rÚ storage_metazStorageWriter.storage_metas €ðˆtr©N)rrrÚ__doc__ÚabcÚabstractmethodrÚstrÚosÚPathLiker%Úboolrr+r r0Úlistr4r rrr8rr<Ú classmethodrArr rDrrrrrs€€€€€ððð" Ôð ð  5¨¨b¬k¸4Ð)?Ô#@ð ÈDð ð ð ñÔð ð" Ôð  Ø"ð  Ø+.ð  Ø:=ð  à ð  ð  ð  ñÔð  ð Ôð   xð  °Hð  ð  ð  ñÔð  ð Ô𠨨h¬ð ¸DÀ¼Nð ð ð ñÔð ð  Ôð Øð Ø'2ð à [Ô!Ô "ð ð ð ñÔð ð. Ôð ˜xð °$°t¸KÔ7HÔ2Ið Èdð ð ð ñÔð ð ØÔð °5¸¸b¼kÐ9IÔ3Jð Ètð ð ð ñÔñ„[ð ð˜h {Ô3ððððððrrc ó¸—eZdZdZejddeeej dfddfd„¦«Z ejde de de fd„¦«Z ejd e d ede de ddf d „¦«Zejd edefd „¦«Zejdeedeefd„¦«Zejd edededfd„¦«Zeejdeeej fdefd„¦«¦«ZdS)raV Interface used by ``load_state_dict`` to read from storage. One StorageReader instance acts as both the coordinator and the follower in a distributed checkpoint. As part of initialization, each instance is told its role. A subclass should expected the following sequence of calls by ``load_state_dict``: 0) (all ranks) set checkpoint_id if users pass a valid checkpoint_id. 1) (all ranks) read_metadata() 2) (all ranks) set_up_storage_reader() 3) (all ranks) prepare_local_plan() 4) (coordinator) prepare_global_plan() 5) (all ranks) read_data() Nr r!có—dS)a± Calls to indicates a brand new checkpoint read is going to happen. A checkpoint_id may be present if users set the checkpoint_id for this checkpoint read. The meaning of the checkpiont_id is storage-dependent. It can be a path to a folder/file or a key for a key-value storage. Args: checkpoint_id (Union[str, os.PathLike, None]): The ID of this checkpoint instance. The meaning of the checkpoint_id depends on the storage. It can be a path to a folder or to a file. It can also be a key if the storage is more like a key-value store. (Default: ``None``) Nrr#s rr%zStorageReader.resetºr&rr(r)có—dS)z Read the checkpoint metadata. Returns: The metadata object associated with the checkpoint being loaded. Nr)r$r(r)s rÚ read_metadatazStorageReader.read_metadataÌr,rr9r'có—dS)zî Initialize this instance. Args: metadata (Metadata): The metadata schema to use. is_coordinator (bool): Whether this instance is responsible for coordinating the checkpoint. Nr)r$r9r'r(r)s rÚset_up_storage_readerz#StorageReader.set_up_storage_readerÖr,rr-có—dS)a† Perform storage-specific local planning. While this method can produce a completely different plan, the recommended way is to store storage specific data in LoadPlan::storage_data. Args: plan (LoadPlan): The local plan from the ``LoadPlan`` in use. Returns: A transformed ``LoadPlan`` after storage local planning Nrr/s rr0z StorageReader.prepare_local_planãr,rr1có—dS)aÔ Perform centralized planning of storage loading. This method is only called on the coordinator instance. While this method can produce a completely different plan, the preferred way is to store storage specific data in LoadPlan::storage_data. Args: plans: A list of ``LoadPlan`` instances, one for each rank. Returns: A list of transformed ``LoadPlan`` after storage global planning Nrr3s rr4z!StorageReader.prepare_global_planòr,rr5có—dS)a« Read all items from ``plan`` using ``planner`` to resolve the data. A subclass should call ``LoadPlanner::load_bytes`` to deserialize a BytesIO object into the right place. A subclass should call ``LoadPlanner::resolve_tensor`` to get access to the tensors that in should load data into. It's the StorageLayer responsibility to properly schedule any cross device copies required. Args: plan (LoadPlan): The local plan to execute on planner (LoadPlanner): The planner object to use to resolve items. Returns: A future that completes once all reads are finished. Nrr7s rÚ read_datazStorageReader.read_datar,rcó—dSr>rr?s rrAz$StorageReader.validate_checkpoint_idrBrrE)rrrrFrGrHrrIrJrKr%rrrRrLrTr r0rMr4r rrXrNrArrrrr¨sÙ€€€€€ððð" Ôð ð  5¨¨b¬k¸4Ð)?Ô#@ð ÈDð ð ð ñÔð ð" Ôð  3ð °#ð ¸(ð ð ð ñÔð ð Ôð  Ø ð  Ø26ð  Ø?Bð  ØNQð  à ð  ð  ð  ñÔð  ð Ôð   xð  °Hð  ð  ð  ñÔð  ð Ô𠨨h¬ð ¸DÀ¼Nð ð ð ñÔð ð  Ôð ˜hð °ð ÀÈÄð ð ð ñÔð ð*ØÔð °5¸¸b¼kÐ9IÔ3Jð Ètð ð ð ñÔñ„[ð ð ð rr)rGrJÚ dataclassesrÚtypingrrrÚ%torch.distributed.checkpoint.metadatarrr Ú$torch.distributed.checkpoint.plannerr r r r Ú torch.futuresrÚ__all__rÚABCrrrrrúrasyðØ € € € Ø € € € Ø!Ð!Ð!Ð!Ð!Ð!Ø'Ð'Ð'Ð'Ð'Ð'Ð'Ð'Ð'Ð'àVÐVÐVÐVÐVÐVÐVÐVÐVÐVððððððððððððð !Ð Ð Ð Ð Ð ð <Ð ;Ð ;€ð €$ÐÑÔðððððñôñÔððJðJðJðJðJC”GñJôJðJðZx ðx ðx ðx ðx C”Gñx ôx ðx ðx ðx r