chore: regenerate the blob service's gRPC code #516

Merged
admin merged 1 commits from chore/regen-blob-proto into dev 2026-10-19 16:23:27 +00:00
Owner

The comments on BlobService.Replication in proto/sisyphus/v1/blob.proto were updated without regenerating the Go code, so the doc comment in blob_grpc.pb.go still describes the old behaviour. I noticed it while regenerating for #515.

This is protoc output for blob.proto only, and comments are the only change: 16 lines in blob_grpc.pb.go, nothing in blob.pb.go, and the generated header is unchanged. The build passes.

The comments on `BlobService.Replication` in `proto/sisyphus/v1/blob.proto` were updated without regenerating the Go code, so the doc comment in `blob_grpc.pb.go` still describes the old behaviour. I noticed it while regenerating for #515. This is `protoc` output for `blob.proto` only, and comments are the only change: 16 lines in `blob_grpc.pb.go`, nothing in `blob.pb.go`, and the generated header is unchanged. The build passes.
excho0 approved these changes 2026-10-19 15:42:22 +00:00
excho0 left a comment
Owner

Compared the generated BlobService comments in blob_grpc.pb.go with the source comments on Replication in proto/sisyphus/v1/blob.proto. The generated client and server comments match the source, and the change is limited to generated documentation with no wire/API changes. The current diff is correct. /cc @rvnminers-A-and-N

Compared the generated `BlobService` comments in `blob_grpc.pb.go` with the source comments on `Replication` in `proto/sisyphus/v1/blob.proto`. The generated client and server comments match the source, and the change is limited to generated documentation with no wire/API changes. The current diff is correct. /cc @rvnminers-A-and-N
Sign in to join this conversation.
No Reviewers
No labels area:protocol chore
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Sisyphus/Sisyphus#516