Sam Craig

A quick change from ↴ ```proto syntax = "proto3"; ... ``` to ↴ ```proto syntax = "proto2"; ... ``` ... should do the trick. The reason that you're getting an...

Interesting, just taking a look at [`this`](https://chromium.googlesource.com/external/github.com/protocolbuffers/protobuf/+/refs/heads/master/docs/field_presence.md#presence-in-proto3-apis) write-up on the changes to field presence behaviors in the v3.15 release - that table outlines the `optional` modifier support for the scalar...

Looking at the call stack, starting at [`parseExtension`](https://github.com/protobufjs/protobuf.js/blob/f5b893c03e9694bbe7da7c4001cc74b06039eb9c/src/parse.js#L731): https://github.com/protobufjs/protobuf.js/blob/f5b893c03e9694bbe7da7c4001cc74b06039eb9c/src/parse.js#L749 ↓ https://github.com/protobufjs/protobuf.js/blob/f5b893c03e9694bbe7da7c4001cc74b06039eb9c/src/parse.js#L396 ↓ https://github.com/protobufjs/protobuf.js/blob/f5b893c03e9694bbe7da7c4001cc74b06039eb9c/src/namespace.js#L218 So it looks like namespace extensions aren't compatible with `optional` modifiers whatsoever in `proto3`. Did a quick...

> I don't think you're interpreting that correctly either. The table you linked has two entries for "Singular numeric (integer or floating point)", one with `optional` and one without, which...

Running into a similar problem on Win11 21H2, running as admin looks to be the only solve that I've come up with. p.s. Love the app!

Currently running it via a scheduled task at log in to bump the process up to admin privs.