Tooling · rule
registry.unreachable
The registry couldn't be reached, or answered in a way that can't be read.
Area 14, Tooling; not declinable; the next step is usually the human's.
Why Jadpo refuses it
jadpo package add and update from the registry, search, audit and
publish ask the registry at https://jadpo.dev/registry/v1/. Every answer
is held to the protocol's table, and one that doesn't fit is treated as no
answer rather than guessed at. Nothing is installed or changed.
jadpo check and jadpo build never go online, so an app already holding
its packages isn't affected.
JADPO_REGISTRY names a stand-in for the registry, over HTTPS, or plain
HTTP on this machine only: another machine over plain HTTP is never tried.
What it looks like
There is no network:
jadpo package add @acme/postcodeserror The registry couldn't be read
- reason
jadpo.devcouldn't be found.- next
- Check your connection, then run the command again (human)
- rule
- registry.
unreachable - help
- https://jadpo.
dev/docs/errors/registry. unreachable
(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: an agent can't change your network.
How to fix it
If the network is down, or the address is wrong, fix that and run the
command again. Check JADPO_REGISTRY if it is set, which has to end in
/registry/v1/:
env | grep JADPO_REGISTRYThe command then reads the registry as it would have, and nothing was changed in the meantime.
Related
Markdown for agents: /docs/errors/registry.unreachable.md.Built from Jadpo main at 0e6fe62.