Skip to content

Conversation

@GinSiuCheng
Copy link

Adjust the go package declared in the proto definition to agree with the go package of the checked in generated proto code at https://github.com/google/certificate-transparency-go/blob/master/client/configpb/multilog.pb.go

@GinSiuCheng GinSiuCheng requested a review from a team as a code owner December 9, 2025 19:14
@GinSiuCheng GinSiuCheng requested review from roger2hk and removed request for a team December 9, 2025 19:14
nop761

This comment was marked as spam.

@roger2hk
Copy link
Contributor

roger2hk commented Dec 9, 2025

You can run the following command to regenerate the proto files.

docker build -f ./integration/Dockerfile -t ctgo-builder .
docker run -it --mount type=bind,src="$(pwd)",target=/src ctgo-builder /bin/bash -c "cd /src; ./scripts/install_deps.sh; go generate -x ./..."

@GinSiuCheng
Copy link
Author

Regenerating the proto file with that command will have no effect, the location of the generated proto file is the problem and not its contents. Changing the declaration within the proto file is the easier fix, rather than changing all the code that refers to it

@roger2hk
Copy link
Contributor

The following content in the generated proto go file will be changed after the regeneration.

"\x0fnot_after_limit\x18\x04 \x01(\v2\x1a.google.protobuf.TimestampR\rnotAfterLimitBHZFgithub.com/google/certificate-transparency-go/client/multilog/configpbb\x06proto3"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants