Proto commits in mlcommons/chakra

These 17 commits are when the Protocol Buffers files have changed:

2026-07-07

Consolidate framework-level node types into DATA_OP_NODE. Use op_info oneof to store either StorageInfo or DataOpType.

The documentation is generated from this commit.

2026-06-17

Drop parent/child node-type comments from NodeType enum Remove the comments coupling STORAGE_NODE to the framework-level parent nodes: tracing may capture only framework-level nodes, or only storage operations, so the asserted relationship is not mandatory. Per review feedback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-16

Move storage operations into storage.proto Extract StorageLevel, StorageInfo, FsOp, PageOp, and BlockOp into a new storage.proto and import it from et_def.proto, per review feedback (#171). protoc's --python_out emits flat absolute imports between generated modules (et_def_pb2 contains `import storage_pb2`), which fail under the installed chakra.schema.protobuf package. Add schema/protobuf/__init__.py that puts the package directory on sys.path so the generated cross-imports resolve. See protocolbuffers/protobuf#1491. Register storage.proto in setup.cfg (proto_files + grpc_files) and pyproject package-data so it is compiled and shipped alongside et_def.proto. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Rename inner Op enum to OpType in storage op messages Rename the nested Op enum to OpType in FsOp, PageOp, and BlockOp so it no longer reads ambiguously next to the FsOp message name, per review feedback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Rework storage node types into framework-level parents and storage ops Rename BATCH_NODE to DATALOADER_NODE and add KV_TRANSFER_NODE so dataloader, checkpoint, and KV-transfer ops each have a distinct framework-level parent node type, per review feedback. STORAGE_NODE remains the lower-level storage operation emitted under those parents. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-27

Add storage operations to et_def.proto

2024-05-09

Reorganize directories

2023-10-10

[chakra][et_def] Add version field Summary: Add version field Reviewed By: shengbao Differential Revision: D50082609

[chakra][et_def] Update the Chakra schema Summary: * Transition from proto2 to proto3 * Removed "required" or "optional" keywords * Updated AttributeProto to incorporate all data types in proto3 * Renamed parent to data_dep & ctrl_dep * Updated CollectiveCommType so that it can incorporate all collective communication types * Added "Message Tensor" to encode tensor information * Updated the input / output data types to message IOInfo * Added operator start time and duration Reviewed By: lofe Differential Revision: D48790087

2023-08-07

[chakra] support broadcast collective communication Summary: Support broadcast collective communication Reviewed By: shengbao Differential Revision: D48032038

2023-08-05

[chakra][et_def] addition of uint64 to AttributeProto Summary: In this commit, I have extended the data types of AttributeProto to include uint64. Prior to this change, AttributeProto lacked support for the uint64 data type. Reviewed By: shengbao Differential Revision: D47952700

2023-08-03

[chakra][et_def] add GlobalMetadata to track global metadata Summary: While PyTorch execution traces have global metadata such as schema, pid, time, and start_ts, Chakra execution traces do not. I have introduced the ExecutionTrace message to track global metadata. Reviewed By: zhaodongwang Differential Revision: D47795237

2023-07-27

[chakra][et_def] change 'strings' field type from 'bytes' to 'string' in AttributeProto Summary: Updated the data type in AttributeProto: Changed 'strings' field from 'repeated bytes' to 'repeated string'. Reviewed By: lofe Differential Revision: D47636929

2023-07-07

[et_def] update schema to v0.0.3

2023-07-01

[et_def] update schema to v0.0.2

2023-06-01

[et_def] rename eg_def to et_def

2023-02-01

[eg_def] add execution graph definition