2024-02-24 12:28:55 +01:00
|
|
|
@llama.cpp
|
2024-03-02 22:00:14 +01:00
|
|
|
@security
|
2024-02-24 12:28:55 +01:00
|
|
|
Feature: Security
|
|
|
|
|
|
|
|
Background: Server startup with an api key defined
|
|
|
|
Given a server listening on localhost:8080
|
2024-03-02 22:00:14 +01:00
|
|
|
And a model file tinyllamas/stories260K.gguf from HF repo ggml-org/models
|
2024-02-24 12:28:55 +01:00
|
|
|
And a server api key llama.cpp
|
|
|
|
Then the server is starting
|
|
|
|
Then the server is healthy
|
|
|
|
|
|
|
|
Scenario Outline: Completion with some user api key
|
|
|
|
Given a prompt test
|
|
|
|
And a user api key <api_key>
|
|
|
|
And 4 max tokens to predict
|
|
|
|
And a completion request with <api_error> api error
|
|
|
|
|
|
|
|
Examples: Prompts
|
|
|
|
| api_key | api_error |
|
|
|
|
| llama.cpp | no |
|
|
|
|
| llama.cpp | no |
|
|
|
|
| hackeme | raised |
|
|
|
|
| | raised |
|
|
|
|
|
|
|
|
Scenario Outline: OAI Compatibility
|
|
|
|
Given a system prompt test
|
|
|
|
And a user prompt test
|
|
|
|
And a model test
|
|
|
|
And 2 max tokens to predict
|
|
|
|
And streaming is disabled
|
|
|
|
And a user api key <api_key>
|
|
|
|
Given an OAI compatible chat completions request with <api_error> api error
|
|
|
|
|
|
|
|
Examples: Prompts
|
|
|
|
| api_key | api_error |
|
|
|
|
| llama.cpp | no |
|
|
|
|
| llama.cpp | no |
|
|
|
|
| hackme | raised |
|
|
|
|
|
json-schema-to-grammar improvements (+ added to server) (#5978)
* json: fix arrays (disallow `[,1]`)
* json: support tuple types (`[number, string]`)
* json: support additionalProperties (`{[k: string]: [string,number][]}`)
* json: support required / optional properties
* json: add support for pattern
* json: resolve $ref (and support https schema urls)
* json: fix $ref resolution
* join: support union types (mostly for nullable types I think)
* json: support allOf + nested anyOf
* json: support any (`{}` or `{type: object}`)
* json: fix merge
* json: temp fix for escapes
* json: spaces in output and unrestricted output spaces
* json: add typings
* json:fix typo
* Create ts-type-to-grammar.sh
* json: fix _format_literal (json.dumps already escapes quotes)
* json: merge lit sequences and handle negatives
{"type": "string", "pattern": "^({\"question\": \"[^\"]+\", \"response\": \"[^\"]+\"}\\n)+$"}
* json: handle pattern repetitions
* Update json-schema-to-grammar.mjs
* Create regex-to-grammar.py
* json: extract repeated regexp patterns to subrule
* Update json-schema-to-grammar.py
* Update json-schema-to-grammar.py
* Update json-schema-to-grammar.py
* json: handle schema from pydantic Optional fields
* Update json-schema-to-grammar.py
* Update json-schema-to-grammar.py
* Update ts-type-to-grammar.sh
* Update ts-type-to-grammar.sh
* json: simplify nullable fields handling
* json: accept duplicate identical rules
* json: revert space to 1 at most
* json: reuse regexp pattern subrules
* json: handle uuid string format
* json: fix literal escapes
* json: add --allow-fetch
* json: simplify range escapes
* json: support negative ranges in patterns
* Delete commit.txt
* json: custom regex parser, adds dot support & JS-portable
* json: rm trailing spaces
* Update json-schema-to-grammar.mjs
* json: updated server & chat `( cd examples/server && ./deps.sh )`
* json: port fixes from mjs to python
* Update ts-type-to-grammar.sh
* json: support prefixItems alongside array items
* json: add date format + fix uuid
* json: add date, time, date-time formats
* json: preserve order of props from TS defs
* json: port schema converter to C++, wire in ./server
* json: nits
* Update json-schema-to-grammar.cpp
* Update json-schema-to-grammar.cpp
* Update json-schema-to-grammar.cpp
* json: fix mjs implementation + align outputs
* Update json-schema-to-grammar.mjs.hpp
* json: test C++, JS & Python versions
* json: nits + regen deps
* json: cleanup test
* json: revert from c++17 to 11
* json: nit fixes
* json: dirty include for test
* json: fix zig build
* json: pass static command to std::system in tests (fixed temp files)
* json: fix top-level $refs
* json: don't use c++20 designated initializers
* nit
* json: basic support for reserved names `{number:{number:{root:number}}}`
* Revamp test cmake to allow args (WORKING_DIRECTORY needed for JSON test)
* json: re-ran server deps.sh
* json: simplify test
* json: support mix of additional props & required/optional
* json: add tests for some expected failures
* json: fix type=const in c++, add failure expectations for non-str const&enum
* json: test (& simplify output of) empty schema
* json: check parsing in test + fix value & string refs
* json: add server tests for OAI JSON response_format
* json: test/fix top-level anyOf
* json: improve grammar parsing failures
* json: test/fix additional props corner cases
* json: fix string patterns (was missing quotes)
* json: ws nit
* json: fix json handling in server when there's no response_format
* json: catch schema conversion errors in server
* json: don't complain about unknown format type in server if unset
* json: cleaner build of test
* json: create examples/json-schema-pydantic-example.py
* json: fix date pattern
* json: move json.hpp & json-schema-to-grammar.{cpp,h} to common
* json: indent 4 spaces
* json: fix naming of top-level c++ function (+ drop unused one)
* json: avoid using namespace std
* json: fix zig build
* Update server.feature
* json: iostream -> fprintf
* json: space before & refs for consistency
* json: nits
2024-03-21 12:50:43 +01:00
|
|
|
Scenario Outline: OAI Compatibility (invalid response formats)
|
|
|
|
Given a system prompt test
|
|
|
|
And a user prompt test
|
|
|
|
And a response format <response_format>
|
|
|
|
And a model test
|
|
|
|
And 2 max tokens to predict
|
|
|
|
And streaming is disabled
|
|
|
|
Given an OAI compatible chat completions request with raised api error
|
|
|
|
|
|
|
|
Examples: Prompts
|
|
|
|
| response_format |
|
|
|
|
| {"type": "sound"} |
|
|
|
|
| {"type": "json_object", "schema": 123} |
|
|
|
|
| {"type": "json_object", "schema": {"type": 123}} |
|
|
|
|
| {"type": "json_object", "schema": {"type": "hiccup"}} |
|
|
|
|
|
2024-02-24 12:28:55 +01:00
|
|
|
|
|
|
|
Scenario Outline: CORS Options
|
2024-03-09 11:27:53 +01:00
|
|
|
Given a user api key llama.cpp
|
|
|
|
When an OPTIONS request is sent from <origin>
|
|
|
|
Then CORS header <cors_header> is set to <cors_header_value>
|
2024-02-24 12:28:55 +01:00
|
|
|
|
|
|
|
Examples: Headers
|
|
|
|
| origin | cors_header | cors_header_value |
|
|
|
|
| localhost | Access-Control-Allow-Origin | localhost |
|
|
|
|
| web.mydomain.fr | Access-Control-Allow-Origin | web.mydomain.fr |
|
|
|
|
| origin | Access-Control-Allow-Credentials | true |
|
|
|
|
| web.mydomain.fr | Access-Control-Allow-Methods | POST |
|
|
|
|
| web.mydomain.fr | Access-Control-Allow-Headers | * |
|