GitLab

The `stop` option to the generate API is a list of sequences that should cause generation to stop. Although these are commonly called "stop tokens", they do not necessarily correspond to LLM tokens (per the LLM's tokenizer). For example, if the caller sends a generate request with `"stop":["\n"]`, then generation should stop on any token containing `\n` (and trim `\n` from the output), not just if the token exactly matches `\n`. If `stop` were interpreted strictly as LLM tokens, then it would require callers of the generate API to know the LLM's tokenizer and enumerate many tokens in the `stop` list.

Fixes https://github.com/jmorganca/ollama/issues/295.

The token printed for authorized requests has a lifetime of 1h. If an
upload exceeds 1h, a chunk push will fail since the token is created on
a "start upload" request.

This replaces the Pipe with SectionReader which is simpler and
implements Seek, a requirement for makeRequestWithRetry. This is
slightly worse than using a Pipe since the progress update is directly
tied to the chunk size instead of controlled separately.

- re-use previously evaluated embeddings when possible
- change embeddings digest identifier to be based on model name and embedded file path

- defer closing llm on embedding
- do not override licenses
- remove debugging print line
- reformat model file docs

- default to embeddings enabled
- move embedding logic for loaded model to request
- allow embedding full directory
- close llm on reload

Fixes #297
Fixes #296

switch to a monolithic upload instead of a chunk upload through a pipe
to report progress