Latest docs.podman.io Reference page has a circular dependency. #22351
Assignees
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
Merged
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Apr 12, 2024
Commit 668d517 moved a lot of type definitions and by that also copied a bucnh of swagger:model comments, this caused swagger to create a incorrect yaml that can no longer be parsed by redoc due "Self-referencing circular pointer". The yaml basically defined the type with a name and the pointed to the same name definition again so it caused a infinitive recursion where redoc just throws an error but the swagger style ignored the case so it seemed like it worked but obviously the type information was not working. Fixes containers#22351 Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Apr 16, 2024
Commit 668d517 moved a lot of type definitions and by that also copied a bucnh of swagger:model comments, this caused swagger to create a incorrect yaml that can no longer be parsed by redoc due "Self-referencing circular pointer". The yaml basically defined the type with a name and the pointed to the same name definition again so it caused a infinitive recursion where redoc just throws an error but the swagger style ignored the case so it seemed like it worked but obviously the type information was not working. Fixes containers#22351 Signed-off-by: Paul Holzinger <[email protected]>
stale-locking-app
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Description
When going to this URL https://docs.podman.io/en/latest/_static/api.html, you receive:
This can also happen if you go to docs.podman.io->reference->latest
This appears to be an issue only with latest, the other links on that page pointing to particular versions are working fine.
@baude any thoughts?
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Error page
Describe the results you expected
API documentation page
podman info output
N/APodman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: