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
The Rolodex created still throws errors that no file systems have been configured
{"time":"2024-10-01T21:17:26.857755475Z","level":"ERROR","msg":"unable to open the rolodex file, check specification references and base path","file":"/home/luke/github/vacuum/functions/openapi/test-param.yaml","error":"rolodex has no file systems configured, cannot open '/home/luke/github/vacuum/functions/openapi/test-param.yaml'. Add a BaseURL or BasePath to your configuration so the rolodex knows how to resolve references"}
So I suspect there is a little more setup needed here.
The text was updated successfully, but these errors were encountered:
I may have found the source a bug we have been troubleshooting internally, but I suspect it may actually be sourced in the vacuum rule logic.
I first had the issue on my own, in the plex-api-spec the sectionKey parameter detailed there is what the vacuum rule flagged on.
I've dug through and managed to replicate the error in the
path_parameters_test.go
file in vacuum as well with this snippet:The
test-param.yaml
file in this context is just the contents of the ember param.This successfully replicates the error:
I believe the issue is that in this setup/vacuum flow the rolodex is not properly being initialized prior to lookups occurring.
Running through debug I was able to trace it down to this error message when a lookup attempt is made:
Here is that call stack at that point:
Digging into the test setup, This line seems to imply the
Rolodex
should already be initialized at this pointBut even adding a
nil
check and manualRolodex
initializationThe
Rolodex
created still throws errors that no file systems have been configuredSo I suspect there is a little more setup needed here.
The text was updated successfully, but these errors were encountered: