GitLab

Fix/issue 3736: When runners are closing or expiring. Scheduler is getting dirty VRAM size readings.

log when the waiting for the process to stop to help debug when other tasks execute during this wait.
expire timer clear the timer reference because it will not be reused.
close will clean up expireTimer if calling code has not already done this.

fix runner expire during active use.  Clearing the expire timer as it is used.  Allowing the finish to assign an expire timer so that the runner will expire after no use.

Co-authored-by: Blake Mizerany <blake.mizerany@gmail.com>

- return descriptive error messages when unauthorized to create blob or push a model
- display the local public key associated with the request that was denied

Updated the code a bit

* Bump llama.cpp to b2761

* Adjust types for bump

Fix relative path lookup

* app: restart server on failure

* fix linter

* address comments

* refactor log directory creation to be where logs are written

* check all log dir creation errors

Add support for building on Windows ARM64

Fix concurrency for CPU mode

Prior refactoring passes accidentally removed the logic to bypass VRAM
checks for CPU loads.  This adds that back, along with test coverage.

This also fixes loaded map access in the unit test to be behind the mutex which was
likely the cause of various flakes in the tests.

The Digest type needs more thought and is not necessary at the moment.