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 sphinx-build -b needs <source_dir> <output_dir> -c <conf_dir> command issues the following warning at the end:
WARNING: Could not load needs json file <conf_dir>/needs.json
not sure if the directory is actually the directory of the conf.py or just the directory that you call sphinx-build in (those happen to be the same for me). Anyhow, I have not set needs_file, so there is no "needs.json" to load from by intention.
Maybe this is related to needs_file, but then I doubt that a warning is justiefied - I simply do not need the feature store different versions in my needs.json.
The text was updated successfully, but these errors were encountered:
There is a default configuration, which defines where a need.json is stored.
And this file then gets reused.
If nothing is there, you get this warning.
Typically only on the first run, as this creates the needs.json, which then is reused during the next runs.
We have two options here:
Keep the message, but it's not a Warning. However, it may be relevant for some use cases, where you expect an already existing needs.json.
Set no default value for need_file. So a user must explicitly set this value, if it shall be used.
I would go with 2) and check, if a file like "needs.json" exists.
If this is the case, but needs_file is not set, a small hint is written. Like: "needs.json found, but it will not be used as long as needs_file is not configured".
The
sphinx-build -b needs <source_dir> <output_dir> -c <conf_dir>
command issues the following warning at the end:not sure if the directory is actually the directory of the conf.py or just the directory that you call sphinx-build in (those happen to be the same for me). Anyhow, I have not set needs_file, so there is no "needs.json" to load from by intention.
Maybe this is related to needs_file, but then I doubt that a warning is justiefied - I simply do not need the feature store different versions in my needs.json.
The text was updated successfully, but these errors were encountered: