Repository navigation
Tourwright 2.6.1
A sandbox that checks every connection of the browser, renders that stop at their time limit, and fixes to
the API, voices, nested steps and the browser lock.
Fixed
- Sandbox:
[::ffff:127.0.0.1]and the other ways of writing a private IPv4 inside an IPv6 address (NAT64, 6to4,
compatible) were let through byTOURWRIGHT_BLOCK_PRIVATE, and so were all offe80::/10, multicast and
reserved ranges. - Sandbox: a redirect to a private or not allowed host, a WebSocket and a name that resolved elsewhere a moment
after it was checked (DNS rebinding) were not checked. WithTOURWRIGHT_ALLOWED_HOSTSor
TOURWRIGHT_BLOCK_PRIVATE, every connection of the browser now goes through a proxy that checks it and connects
to the address it checked. - Webhooks no longer follow redirects, and connect to the address the network policy checked.
- An API or MCP asset named
script.jsonreplaced the checked script. - API job
optionsare checked when the job is created (width/height320–3840, a knownqualityand
capture, a voice name,dryRun/safeas booleans): a bad one is a 400 that names the field, not a failed
render minutes later. GET /v1/jobs?limit=with a value that is not a whole number above zero returned nothing, or almost every job:
it now gets the default (50).HEADon a file with aRangeheader sent the file's bytes.- A
TOURWRIGHT_LINK_TTLthat is not a number made download links that never expired; with the API on::the
links pointed tohttp://:::port. - A worker on a host whose name has dots (
worker.example.com) put the jobs of a stopped worker back in the local
queue under a wrong name. - A slides
theme.backgroundwent into an ffmpeg filter as written, so a script could add filters of its own
(movie=reads a file of the server): only a color gets there now. - A render past its time limit went on in the background (browser open) while its work folder was deleted: it
now stops. A worker that kills a render at the limit also ends the browser and ffmpeg it started. - A step inside
if,tryoroffCamerawas named by its place inside the block (step 2); it is now
step 4.2, in errors,checkand its report. tourwright guide(andnarrate) failed on a script withexport: [audio]or[silent].TOURWRIGHT_TTS_COMMANDbroke on a cache path with spaces (common on Windows):{out}is quoted for the shell,
andTOURWRIGHT_TTS_VOICE/TOURWRIGHT_TTS_OUTcarry the same values.- The browser lock outside Linux could fail when it was released at the wrong moment, take a lock whose owner had
not written its pid yet, or let two waiters take a dead owner's lock at once. - Sentences cached with an OpenAI-compatible model, a TTS command or a Pocket voice recording that later changed
were reused: those settings are now part of the cache key (other engines keep their cache). Plugin engines can
add theirs withfingerprint.