llama.cpp/examples/json_schema_pydantic_example.py at master

nwpie/llama.cpp

Fork 0

mirror of https://github.com/ggerganov/llama.cpp.git synced 2026-02-05 13:53:23 +02:00

Files

compilade 3fd62a6b1c

Nix aarch64 builds / nix-build-aarch64 (push) Waiting to run

Nix CI / nix-eval (macos-latest) (push) Waiting to run

Nix CI / nix-eval (ubuntu-latest) (push) Waiting to run

Nix CI / nix-build (macos-latest) (push) Waiting to run

Nix CI / nix-build (ubuntu-latest) (push) Waiting to run

flake8 Lint / Lint (push) Waiting to run

Python check requirements.txt / check-requirements (push) Has been cancelled

Python Type-Check / pyright type-check (push) Has been cancelled

py : type-check all Python scripts with Pyright (#8341 )

* py : type-check all Python scripts with Pyright

* server-tests : use trailing slash in openai base_url

* server-tests : add more type annotations

* server-tests : strip "chat" from base_url in oai_chat_completions

* server-tests : model metadata is a dict

* ci : disable pip cache in type-check workflow

The cache is not shared between branches, and it's 250MB in size,
so it would become quite a big part of the 10GB cache limit of the repo.

* py : fix new type errors from master branch

* tests : fix test-tokenizer-random.py

Apparently, gcc applies optimisations even when pre-processing,
which confuses pycparser.

* ci : only show warnings and errors in python type-check

The "information" level otherwise has entries
from 'examples/pydantic_models_to_grammar.py',
which could be confusing for someone trying to figure out what failed,
considering that these messages can safely be ignored
even though they look like errors.

2024-07-07 15:04:39 -04:00

3.1 KiB

Raw Permalink Blame History

View Raw

3.1 KiB Raw Permalink Blame History

3.1 KiB

Raw Permalink Blame History