- 14 Nov, 2024 5 commits
-
-
Jesse Gross authored
It's possible to get prompts that consist entirely of whitespace - this is most likely to happen when generating embeddings. Currently, we will trim this away, leaving an empty prompt, which will then generate an error. Generating embeddings from whitespace should not trigger an error, as this may break pipelines. It's better to just leave the whitespace in place and process what we are given. This is consistent with past versions of Ollama. Bug #7578
-
Jesse Gross authored
NUM_PARALEL is currently enforced by the Ollama server process - it will only issue requests to the runner if the maximum number of concurrent requests has not been exceeded. Although this should be sufficient, it is good for the runner to protect its own data structures. Currently, if too many requests get through to the runner, they will just get stuck and never return. This may help with reports of Ollama hanging, though it is unclear how it would actually occur. Bug #7573
-
Michael Yang authored
fix(mllama): sync backend between batches
-
Blake Mizerany authored
-
Michael Yang authored
-
- 12 Nov, 2024 8 commits
-
-
Jesse Gross authored
-
Daniel Hiltgen authored
It looks like 8 minutes isn't quite enough and we're seeing sporadic timeouts
-
Daniel Hiltgen authored
This adds support for the Jetson JetPack variants into the Go runner
-
Daniel Hiltgen authored
Docker uses the container filesystem for name resolution, so we can't guide users to use the name of the host group. Instead they must specify the numeric ID.
-
Daniel Hiltgen authored
GPU support can break on some systems after a while. This captures a known workaround to solve the problem.
-
Jesse Gross authored
The structure of the accounting for KV cache shifting was carried over from the old runner but it now doesn't feel natural with the new runner. There are a number of invariants that should hold true but are difficult to reason about. There is at least one bug report that would imply that the invariants are not holding. This reduces the number of implicit assumptions and is more forgiving of unexpected situations. It also improves behavior around which input tokens are kept when truncation occurs. Bug #7545
-
Joey Zheng authored
-
Evan authored
-
- 11 Nov, 2024 4 commits
-
-
Prasad Bhalerao authored
-
Ivo Stoykov authored
-
frances720 authored
-
Evan authored
-
- 10 Nov, 2024 1 commit
-
-
Arhan Busam authored
-
- 08 Nov, 2024 3 commits
-
-
Jesse Gross authored
If we get a request with a zero length image, it will result in an out-of-bounds error when we pass the data to the image encoder.
-
Edward J. Schwartz authored
-
Daniel Hiltgen authored
-
- 07 Nov, 2024 5 commits
-
-
Daniel Hiltgen authored
This should have been in #7347 but was overlooked.
-
Daniel Hiltgen authored
This enables the workaround code only for windows which should help windows users with muliple AMD GPUs
-
Daniel Hiltgen authored
Some users are reporting crashes during nvcuda.dll initialization on windows. This should help narrow down where things are going bad.
-
Daniel Hiltgen authored
Bring consistency with the old generate script behavior
-
Daniel Hiltgen authored
On linux nvcc isn't automatically linking to the same cuda version.
-
- 06 Nov, 2024 3 commits
-
-
Jesse Gross authored
-
Jesse Gross authored
Now that server.cpp is gone, we don't need to keep passing arguments that were only ignored and only kept for compatibility.
-
Jesse Gross authored
The Go runner does not have a problem with supporting parallel requests for most multimodal models. Now that we won't be potentially falling back to server.cpp, this restriction can be lifted. However, the new mllama model can't support parallel requests, so we will need to keep a restriction for that.
-
- 05 Nov, 2024 4 commits
-
-
RAPID ARCHITECT authored
added reddit rate below hexabot, ollama powered reddit search and analysis with streamlit for the intervace
-
Daniel Hiltgen authored
One potential failure mode is an empty file which bubbles up as an EOF error, leading to all pulls and listing operations failing. Instead, continue and warn about the corrupt manifest. This also allows re-pulling the corrupt manifest to repair the system.
-
Jesse Gross authored
Currently we assume that images take 768 tokens of context size for the purposes of clipping old messages that exceed the context window. However, our mllama implementation stores the full image embedding in a single token. As a result, there is significant waste of context space. Ideally, we would handle this more generically and have the implementation report the number of tokens. However, at the moment this would just result in a similar set of 'if' conditions in the runner plus APIs to report it back. So for now, we just keep this simple.
-
Med Marrouchi authored
-
- 04 Nov, 2024 6 commits
-
-
Daniel Hiltgen authored
Avoid excessive log spew and make consistent with chat logging
-
Daniel Hiltgen authored
-
Daniel Hiltgen authored
Github actions matrix strategy can't access env settings
-
Michael Yang authored
update llama3.2 vision memory estimation
-
Daniel Hiltgen authored
-
suncloudsmoon authored
-
- 02 Nov, 2024 1 commit
-
-
Daniel Hiltgen authored
The runtime and management libraries may not always have identical ordering, so use the device UUID to correlate instead of ID.
-