⨯ PR #69 5435458e autodocodec NorfairKing

5435458e

Support min/max-length bounds for strings.

Not sure if this change is a good idea, but I was looking for a way to support minLength/maxLength for JSON specs.
https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-validation-01#name-validation-keywords-for-str

So I tried to follow the standard already established by integer bounds and implemented the similar thing for strings.

Suite timing

	Time to Start	Worker time	Duration	Time to finish	Idle
Config	0s	10s	10s	10s	0s
Eval	4m18s	2m23s	2m23s	6m42s	4m07s
Build	26m05s	46s	-	-	30m01s
Suite	0s	3m21s	-	-	295h10m25s

Timeline

Agent Instructions

This page shows suite timings.

This page is also available in machine-friendly formats. Request one with the Accept header:

curl --netrc -H 'Accept: application/json' https://staging.nix-ci.com/gh:NorfairKing:autodocodec/refs%2Fpull%2F69%2Fmerge/5435458e8749489ba9c94041a7050baabd9396a4/timing
curl --netrc -H 'Accept: text/markdown' https://staging.nix-ci.com/gh:NorfairKing:autodocodec/refs%2Fpull%2F69%2Fmerge/5435458e8749489ba9c94041a7050baabd9396a4/timing

For more instructions, fetch https://staging.nix-ci.com/instructions .