Feature Request: cancel model loading from the web UI
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp, typescript
Research direction
Start with ModelsService.unload() in tools/ui/src/lib/services/models.service.ts, then find the model manager screen and inline model picker mentioned in the issue. Add a Cancel button in both loading contexts and call the existing unload API. Verify that canceling a loading model stops the load and that the existing unload behavior still works.
Written by the indexing model from the issue text.
Description
Prerequisites
- I am running the latest code. Mention the version if possible as well.
- I carefully followed the README.md.
- I searched using keywords relevant to my issue to make sure that I am creating a new issue that is not already open (or closed).
- I reviewed the Discussions, and have a new and useful enhancement to share.
Feature Description
There is no way to cancel the loading of a model from the web UI. llama-server already supports it, since a POST to /models/unload kills the loading child. This issue requests a button to cancel a model while it is loading.
Motivation
A misclick requires waiting for the model to finish loading before it can be unloaded, which for a large model can be a long time.
Possible Implementation
The required API call is the same as the one already used by the web UI to unload models, ModelsService.unload() in tools/ui/src/lib/services/models.service.ts. It only needs to be wired into a Cancel button in the model manager screen and the inline model picker.
- Dominant language
- C++
- Stars
- 134k
- Forks
- 25.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 509
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ggml-org/llama.cpp
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ggml-org/llama.cpp#32276 · 3 comments ·
Maintainers usually reply within 1 day
-
scripts/moe-cache-tune.py: device_room() under-reports free VRAM when a draft model is loadedPossibly taken @marlonferreira1800-hue claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ggml-org/llama.cpp#31911 · 1 comment ·
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
ggml-org/llama.cpp#31601 · 2 comments ·
Maintainers usually reply within 1 day
-
Compile bug: tools/server/server-context.cpp fails to compile with Intel icx/icpx: std::setw missing <iomanip> includePossibly taken @afnan-mojumder claimed this 13 days ago. Openbug-unconfirmed
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ggml-org/llama.cpp#31458 · 1 comment ·
Maintainers usually reply within 1 day
All issues in ggml-org/llama.cpp
Similar issues
-
comp-formats
Difficulty 2/5 Half a day Newbie friendliness 64/100
ClickHouse/ClickHouse#131694 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ETSInitiative/PETSIRD#243 ·
Maintainers usually reply within 1 day
-
bug engine::whispercpp runtime::rocm wg::platform-core
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lemonade-sdk/lemonade#4168 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/rocm-libraries#15866 ·
Maintainers usually reply within 2 days
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computerPossibly taken @viniciusdsandrade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day