You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running buf mod update, I would expect my dependencies to be properly versioned in my buf.lock file. If it's intentional to not support multiple registries, then I would assume an error stating that would be provided.
Current Behavior
The cli panics with a nil pointer dereference. Switching all dependencies to the same registry (in my case I switched them all to the same private registry) the command works fine.
Depending on modules from multiple registries is not supported, but the fact that this panics is definitely a bug we should fix. Thank you for the reproducible example.
On an unknown remote ModuleIdentity may be nil. Use the fallback logic
to select the correct dependency and derive the related module
identity. Fixesbufbuild#2725
On an unknown remote ModuleIdentity may be nil. Use the fallback logic
to select the correct dependency and derive the related module identity.
Fixes#2725
A dial error for an invalid host will now correctly return the error
formatted with a prompt to check the registry:
```
Failure: dial tcp: lookup private.registry: no such host. Are you sure "private.registry" (derived from module name "private.registry/org/dependency") is a Buf Schema Registry?
```
Expected Behavior
Given the following
buf.yaml
file:When running
buf mod update
, I would expect my dependencies to be properly versioned in mybuf.lock
file. If it's intentional to not support multiple registries, then I would assume an error stating that would be provided.Current Behavior
The cli panics with a nil pointer dereference. Switching all dependencies to the same registry (in my case I switched them all to the same private registry) the command works fine.
Steps to Reproduce
buf.yaml
filebuf mod update
The text was updated successfully, but these errors were encountered: