Erik Friese

The second example also panics if the field is explicitly set to the default value. That is, the following snippet panics as well: ```rust let desc = DescriptorPool::global() .get_message_by_name("google.protobuf.BoolValue") .unwrap();...

I see. It just felt counterintuitive to me that functions with very similar names have completely different semantics (when it comes to default values). It also is counterintuitive that asking...

Even without the secrets/encryption aspect, the templates feature would be a great addition to home-manager as there seems to be no "official" way to manage mutable config files yet.

Hi @AdamBryantLaunchWindow, thanks for sharing your workaround! I worked around this issue by downgrading all OpenTelemetry dependencies to 1.24.0. This works as well.

As of version 2.0.0b7, accessing an ordinary unset field gives the default value, whereas accessing an unset field which is part of a oneof group raises an AttributeError: ```protobuf message...

Just for clarification: The pattern shown in the opening post is correctly working as intended. It is just incompatible with typical assumptions made by type checkers (e.g. fields are always...

Oh, I see. The google implementation gives the default value. Apparently, you are supposed to use the `HasField()` method to figure out whether a field is actually set: ```python3 test...

I have the same issue at work (behind a corporate proxy). Based on the suggestions given here (using `rustls_platform_verifier`), I was able to patch uv so that it works in...

Hi @romaingyh, in principle yes - the patch isn't that big of a deal. But I don't have the impression that the uv team wants to have a workaround in...

I think [this](https://github.com/seanmonstar/reqwest/pull/2286) is the PR the uv team is waiting for to solve this issue. It is open since May 2024, and there doesn't seem to be much progress....