-
Notifications
You must be signed in to change notification settings - Fork 15.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid NullReferenceException when accessing CustomOptions #6826
Conversation
Even though the property is deprecated, it still shouldn't throw.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Does this need to be backported to 3.10.x or is it only problem on HEAD? |
I'll double check - I think it's okay in 3.10.1. |
Nope, it turns out it is a problem in 3.10.x. @jtattermusch: Should I merge here, then create a separate PR that cherry-picks to the 3.10.x branch? What about #6824? |
@jskeet can you please create a cherry-pick for 3.10.x? |
@rafi-kamal there seems to be yet another problem with the 3.10.x release - what' the ETA for 3.11.x? (if it's not very soon, we should do another patch release). |
(Note: the test is from protocolbuffers#6826, but the implementation is effectively reverting to an earlier one.)
I've seen an internal discussion about doing a release soon regarding CY, is this something that can go as part of that or does it need an immediate release? I'm traveling now, if needed I'll be happy to do a minor release for this once I'm back on Wednesday. @TeBoring if you need any immediate release related help. |
Even though the property is deprecated, it still shouldn't throw.