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
Environment, CPU architecture, OS, and Version:
Intel Xeon E5-2643 v4, GNU/Linux (Unraid 6.12.10)
Describe the bug
Absolute paths not being respected in model config yaml.
To Reproduce
Create a yaml config that points to an existing model or template file on the system with an absolute path. The path it tries to load will be relative to the models directory.
Expected behavior
The path is not interpreted as relative.
Additional context
Prior to version 2.13.0, I had model files, their configs, and their templates all stored in different directories for better organization (I had a lot, including various quants for different tasks). I had a separate issue with templates from an undocumented change that I was diagnosing when I discovered this.
The text was updated successfully, but these errors were encountered:
Hello Prowler1000, thank you for bringing this issue to our attention in the LocalAI project. I'm a bot, an experiment of @mudler, auditing the tickets opened in this Github project.
I understand that you are experiencing a problem where absolute paths in model configuration yaml files are not being respected, which causes incorrect loading paths when trying to load models or templates using absolute system paths. This issue seems to have started occurring in version 2.13.0.
In order to better assist you, please provide the following information:
Can you provide a sample yaml config that demonstrates the issue? It would be helpful if we could reproduce the problem.
Are there any specific dependencies or configurations related to your environment that might affect this issue? Any unique settings or configurations that could help us identify the root cause?
Once we have this information, we will be able to investigate the issue further and provide appropriate solutions or workarounds.
Thank you for your patience and your contribution to improving LocalAI.
Regards,
The Github Bot Auditor (Experiment of @mudler)
With LOCALAI_MODELS_PATH actually being set to /models/configs.
Prior to v2.13.0 I had everything set up to use relative paths (prefixed with ../), however an issue with the templates being outside the model directory popped up so in fixing that, I decided it would be better to make everything an absolute path.
LocalAI version:
v2.13.0
Environment, CPU architecture, OS, and Version:
Intel Xeon E5-2643 v4, GNU/Linux (Unraid 6.12.10)
Describe the bug
Absolute paths not being respected in model config yaml.
To Reproduce
Create a yaml config that points to an existing model or template file on the system with an absolute path. The path it tries to load will be relative to the models directory.
Expected behavior
The path is not interpreted as relative.
Additional context
Prior to version 2.13.0, I had model files, their configs, and their templates all stored in different directories for better organization (I had a lot, including various quants for different tasks). I had a separate issue with templates from an undocumented change that I was diagnosing when I discovered this.
The text was updated successfully, but these errors were encountered: