Jonas Bushart

It is indeed unfortunate that this always tries to install the package, but I am not aware how to check these things properly in a distro-agnostic version. Another problem I...

Hi @afro-coder, the links above should have examples of what the `CI_JOB_SERVICES` variable contains when being used. It should contain the information from the `services` key in the CI config.

> Seems like Gitlab already exports this `$CUSTOM_ENV_CI_JOB_SERVICES` [docs.gitlab.com/runner/executors/custom.html#services](https://docs.gitlab.com/runner/executors/custom.html#services) Yes, that is the same variable. GitLab supports it already, that is what the merge request in the first comment is...

Hi, thanks for the reply. > The intention is to reply with the SOA in any case where a record is not found, which I thought was standard practice. Yes...

@djc Thanks for the info. I also saw the new release. I will check out what kind of changes there are. I also joined the Discord channel, so I am...

I just ran into this problem as well. I'm still confused how `Authority` and the implementations like `InMemoryAuthority` work together, given that `InMemoryAuthority` has four functions (`search`, `lookup`, `inner_lookup`, `inner_lookup_wildcard`)...

Yes, I will take a look at that. The solution should presumably also be applied to `Message` in `proto`, since that has an almost identical `error_msg` function.

Deserializing into a `&str` requires that the `str` can be borrowed from somewhere. This is only possible in some cases. Usually, that works if you deserialize from a slice or...

Right now you can already use [`serde_path_to_error`](https://docs.rs/serde_path_to_error/) to extract which field caused the error. As a benefit it works right now and with any data format (also toml etc.).

@Roms1383 Sorry, I cannot help. I don't understand what you are implementing.