bug: [Local API Server] model failed to load but the server started successfully

[hantran-co]

Describe the bug

I had a something's amiss bug in threads, it turned out it was because i didn't have enough RAM. Then I went to local API server & started the server & The model showed run successfully but it did not show an active model on the footer:

https://github.com/janhq/jan/assets/89722390/6ad1d6e4-daf7-406b-851f-7de0d1c0503d

Environment details

• Operating System: MacOS Sonoma 14.2
• Jan Version: Jan v0.4.5-216
• Processor: Apple M2
• RAM: 16GBelevant hardware specifics: [e.g., Graphics card, SSD/HDD]

Logs app.log

Solution

As investigated with @Van-QA & @louis-jan, API server sometimes doesn't require an active model to be successfully started to be able to run. So we should handle 2 cases differently:

• Show that the model is not started successfully due to something's amiss bug
• Then show that the API server is sucessfully started

Figma: https://www.figma.com/file/ytn1nRZ17FUmJHTlhmZB9f/Jan-App?type=design&node-id=4073-274875&mode=design&t=3u1JkUwg1y1NMCMp-4

1. Starting server + loading model:

2. Model failed to load but the API server starts successfully:

[LeGitHubDeTai]

good evening I just did the new update and I have the same problem

[Van-QA]

hi @urmauur @louis-jan, minor UI issues, using the My Model popup, when users attempt to start a different model (model B) than the one in the local API Server model dropdown (model A):

1. The loader is still displayed in the name of model A when loading model B: :x:

2. If failed loading the model B, there will be error displayed under the name of model A: :x:

[Van-QA]

Tested and looking good on Jan v0.4.6-274 ✅