Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong error message logging when model_path does not exist #3991

Closed
jopemachine opened this issue Mar 14, 2025 — with Lablup-Issue-Syncer · 0 comments · Fixed by #3990
Closed

Wrong error message logging when model_path does not exist #3991

jopemachine opened this issue Mar 14, 2025 — with Lablup-Issue-Syncer · 0 comments · Fixed by #3990
Assignees

Comments

@jopemachine
Copy link
Member

Summary  

  • When the model path is set to a non-existent directory, errors unrelated to the actual issue may be logged.

Steps to Reproduce  

  1. When creating a new model service, deliberately set the model_path to a non-existent directory.
  2. Check the container logs of the session created by the model service.

Expected Behavior  

  • A log indicating that the model path does not exist should be output.

Actual Behavior  

  • A "not found" error log for the first element of start_command is printed.

Logs/Errors  

  • A "not found" error log for the first element of start_command is printed.
@jopemachine jopemachine self-assigned this Mar 14, 2025
@jopemachine jopemachine changed the title Wrong error message when model_path not exist Wrong error message logging when model_path does not exist Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant