Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MessageOptions in validate.proto uses a reserved extension number

Open
#296 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start with api/src/main/proto/validate/validate.proto and compare MessageOptions with the existing FieldOptions definition. Check the protobuf options documentation for the reserved extension number and verify that the revised proto no longer conflicts with protokt; done means the validate proto remains compatible with both consumers.

Written by the indexing model from the issue text.

Description

The Java control plane validate proto is using extension number 1072.

This extension number is reserved for protokt and causes incompatibilities between the envoy proto and protokt

This MessageOption should be implemented as a message like it is in validate.proto's FieldOptions to prevent this issue

Dominant language
Java
Stars
312
Forks
150
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/java-control-plane

All issues in envoyproxy/java-control-plane

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.