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
{{ message }}
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.
registry.getPaginatedJSON(url, &response) in registry.repositories uses
a URL including protocol, and base URL at the fist call and fetches the list of repositories correctly.
e.g. url = https://myrepository/v2/_catalog
BUT it returns the URL to fetch the next page without the base URL
e.g. /v2/_catalog?last=something&n=100&orderby=
next call to registry.getPaginatedJSON(url, &response) return an error: unsupported protocol scheme ""
I guess the same error will happen for Tags (registry.repositories)
The text was updated successfully, but these errors were encountered:
registry.getPaginatedJSON(url, &response) in registry.repositories uses
a URL including protocol, and base URL at the fist call and fetches the list of repositories correctly.
e.g. url = https://myrepository/v2/_catalog
BUT it returns the URL to fetch the next page without the base URL
e.g. /v2/_catalog?last=something&n=100&orderby=
next call to registry.getPaginatedJSON(url, &response) return an error: unsupported protocol scheme ""
I guess the same error will happen for Tags (registry.repositories)
I fixed it on func (registry *Registry) Repositories() ([]string, error) in repositories.go with
registry.getPaginatedJSON(url, &response) in
registry.repositories
usesa URL including protocol, and base URL at the fist call and fetches the list of repositories correctly.
e.g. url =
https://myrepository/v2/_catalog
BUT it returns the URL to fetch the next page without the base URL
e.g.
/v2/_catalog?last=something&n=100&orderby=
next call to registry.getPaginatedJSON(url, &response) return an error:
unsupported protocol scheme ""
I guess the same error will happen for Tags (
registry.repositories
)The text was updated successfully, but these errors were encountered: