+ –°³j@&ãóî€^RIt^RIt^RIHt^RIHt^RIHtHtH t ^RI H t H t H t Ht^RIHt.ROt]!R R 7!R R44t!R R]P&4t!RR ]P&4tR#)éN)Ú dataclass)ÚAny)ÚMetadataÚ MetadataIndexÚ StorageMeta)ÚLoadPlanÚ LoadPlannerÚSavePlanÚ SavePlanner)ÚFutureÚ WriteResultÚ StorageWriterÚ StorageReaderT)Úfrozencó,a€]tRt^toV3RltRtVtR#)r có><€V^8„dQh/S[;R&S[;R&S[;R&#)éÚindexÚ size_in_bytesÚ storage_data)rÚintr)ÚformatÚ __classdict__s"€Úe/home/luca/screen-checking/.venv/lib/python3.14/site-packages/torch/distributed/checkpoint/storage.pyÚ __annotate__ÚWriteResult.__annotate__s*ø‡‚á ÑññÑñ ñ Ñò ó©N)Ú__name__Ú __module__Ú __qualname__Ú__firstlineno__Ú__annotate_func__Ú__static_attributes__Ú__classdictcell__©rs@rr r sø‡‡„rcó”a€]tRt^toRt]P RV3RlRll4t]P V3RlRl4t]P V3RlRl4t ]P V3R lR l4t ]P V3R lR l4t ]P V3R lRl4t ] ]P V3RlRl44tV3RlRltRtVtR#)ra 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() NcóV<€V^8„dQhRS[S[P,R,RR/#©rÚ checkpoint_idNÚreturn©ÚstrÚosÚPathLike)rrs"€rrÚStorageWriter.__annotate__.ó)ø€÷ ñ ¡3©¯©Õ#4°tÕ#;ð Àtñ rc ó€R#)aI 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 checkpoint_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ÚresetÚStorageWriter.reset-ó€ñ rcó0<€V^8„dQhRS[RS[RS[RR/#)rÚis_coordinatorÚargsÚkwargsr+N)Úboolr)rrs"€rrr0@s-ø€÷  ñ  Ù"ð  Ù+.ð  Ù:=ð  à ñ  rc ó€R#)z‰ Initialize this instance. Args: is_coordinator (bool): Whether this instance is responsible for coordinating the checkpoint. Nr)r4r9r:r;s&&*,rÚset_up_storage_writerÚ#StorageWriter.set_up_storage_writer?ó‚rcó&<€V^8„dQhRS[RS[/#©rÚplanr+)r )rrs"€rrr0Lóø€÷  ñ  ¡xð  ±Hñ  rc ó€R#)aI 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©r4rCs&&rÚprepare_local_planÚ StorageWriter.prepare_local_planKr@rcóF<€V^8„dQhRS[S[,RS[S[,/#©rÚplansr+)Úlistr )rrs"€rrr0[ó#ø€÷ ñ ©©h­ð ¹DÁ½Nñ rc ó€R#)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©r4rKs&&rÚprepare_global_planÚ!StorageWriter.prepare_global_planZr@rcóL<€V^8„dQhRS[RS[RS[S[S[,,/#)rrCÚplannerr+)r r r rLr )rrs"€rrr0ls/ø€÷ ñ Ùð Ù'2ð á ‘‘[Õ!Õ "ñ rc ó€R#)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©r4rCrSs&&&rÚ write_dataÚStorageWriter.write_datakr@rcóJ<€V^8„dQhRS[RS[S[S[,,RR/#)rÚmetadataÚresultsr+N)rrLr )rrs"€rrr0„s,ø€÷ ñ ™xð ±$±t¹KÕ7HÕ2Ið Èdñ rc ó€R#)am 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)r4rYrZs&&&rÚfinishÚStorageWriter.finishƒr@rcóJ<€V^8„dQhRS[S[P,RS[/#©rr*r+©r-r.r/r<)rrs"€rrr0–ó$ø€÷ ñ ±3¹¿¹Õ3Dð Éñ rc ó€R#©zu Check if the given checkpoint_id is supported by the storage. This allows us to enable automatic storage selection. Nr©Úclsr*s&&rÚvalidate_checkpoint_idÚ$StorageWriter.validate_checkpoint_id”ó€ñ rcó.<€V^8„dQhRS[R,/#)rr+N)r)rrs"€rrr0sø€÷ñ™k¨DÕ0ñrc ó€R#)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)r4s&rÚ storage_metaÚStorageWriter.storage_metas€ñrr©N)rr r!r"Ú__doc__ÚabcÚabstractmethodr5r>rGrPrVr\Ú classmethodrfrkr$r%r&s@rrrs×ø‡€ñð" ×Ñ÷ ñ óð ð" ×Ñ÷  óð  ð ×Ñ÷  óð  ð ×Ñ÷ óð ð  ×Ñ÷ óð ð. ×Ñ÷ óð ð Ø×Ñ÷ óóð ÷örcó‚a€]tRt^¨toRt]P RV3RlRll4t]P V3RlRl4t]P V3RlRl4t ]P V3R lR l4t ]P V3R lR l4t ]P V3R lRl4t ] ]P V3RlRl44tRtVtR#)ra$ 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 expect 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() NcóV<€V^8„dQhRS[S[P,R,RR/#r)r,)rrs"€rrÚStorageReader.__annotate__»r1rc ó€R#)aQ 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 checkpoint_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``) Nrr3s&&rr5ÚStorageReader.resetºr7rcó,<€V^8„dQhRS[RS[RS[/#)rr:r;r+)rr)rrs"€rrrtÍs"ø€÷ ñ ¡3ð ±#ð ¹(ñ rc ó€R#)zo Read the checkpoint metadata. Returns: The metadata object associated with the checkpoint being loaded. Nr)r4r:r;s&*,rÚ read_metadataÚStorageReader.read_metadataÌr@rc ó6<€V^8„dQhRS[RS[RS[RS[RR/#)rrYr9r:r;r+N)rr<r)rrs"€rrrt×s5ø€÷  ñ  Ù ð  Ù26ð  Ù?Bð  ÙNQð  à ñ  rc ó€R#)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)r4rYr9r:r;s&&&*,rÚset_up_storage_readerÚ#StorageReader.set_up_storage_readerÖr@rcó&<€V^8„dQhRS[RS[/#rB)r)rrs"€rrrtärDrc ó€R#)aF 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 NrrFs&&rrGÚ StorageReader.prepare_local_planãr@rcóF<€V^8„dQhRS[S[,RS[S[,/#rJ)rLr)rrs"€rrrtórMrc ó€R#)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 NrrOs&&rrPÚ!StorageReader.prepare_global_planòr@rcó:<€V^8„dQhRS[RS[RS[R,/#)rrCrSr+N)rr r )rrs"€rrrts&ø€÷ ñ ™hð ±ð ÁÈÅñ rc ó€R#)aC 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. NrrUs&&&rÚ read_dataÚStorageReader.read_datar@rcóJ<€V^8„dQhRS[S[P,RS[/#r_r`)rrs"€rrrtrarc ó€R#rcrrds&&rrfÚ$StorageReader.validate_checkpoint_idrhrrrm)rr r!r"rnrorpr5ryr}rGrPr‡rqrfr$r%r&s@rrr¨sÍø‡€ñð" ×Ñ÷ ñ óð ð" ×Ñ÷ óð ð ×Ñ÷  óð  ð ×Ñ÷  óð  ð ×Ñ÷ óð ð  ×Ñ÷ óð ð*Ø×Ñ÷ óóö r)r rr)ror.Ú dataclassesrÚtypingrÚ%torch.distributed.checkpoint.metadatarrrÚ$torch.distributed.checkpoint.plannerrr r r Ú torch.futuresr Ú__all__r ÚABCrrrrrÚr“spðÛ Û Ý!ÝçVÑV÷óõ !ò <€ñ $Ô÷ðóðôJC—G‘GôJôZx C—G‘Göx r