dev.knotless.getRunOutput

What a running check's steps printed, as its runner sent it (dev.knotless.putRunOutput): the text after a cursor, the steps that ended and the one going, for a client that follows no server-sent events. The appview keeps the last megabyte of a run in memory while it runs, and a while after; the check's record keeps its log. With nothing new and the run going, it waits up to `wait` seconds for more. Answers as dev.knotless.getCheck does for the same viewer: anyone may read a public repository's, its members a private one's.

Details · query
Kindquery
Authorityknotless.dev
Commit rev3mzwyeqg7z2ac
Indexed

Query

query · GET

Parameters

query string

cursor

string

Where an earlier answer ended: only what was printed after it is given. With none, or one of another run of the check, as a rerun at the same commit is, all that is kept.

  • maxLength: 128

repo

requiredstring · at-uri

The repository's dev.knotless.repo record, as dev.knotless.getCheck takes it.

uri

requiredstring · at-uri

The dev.knotless.check record, by a runner the repository names.

wait

integer

Seconds to wait for more when nothing was printed after `cursor` and the run has not ended.

  • minimum: 0
  • maximum: 25

Output

application/json

cursor

requiredstring

Where `text` ends, in this run: given back, it asks for what comes after.

ended

requiredboolean

Whether the run's steps are over: its record is filed with its result in a moment.

going

string

The name of the step running now: none between steps.

steps

requiredarray

The steps that ended so far, as the check's record will say.

itemsref

text

requiredstring

What the steps printed after `cursor`, each step's after a line `==> <name>`, in whole lines masked as the log is: nothing before the runner first sends.

Errors

InvalidRequest

`uri` names no dev.knotless.check record.

NotFound

No such repository, no such check of it by a runner it names, or as many runs followed as the appview keeps.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A runner's word to the appview of what a check it runs is printing, as it prints it.

  • A check of one of a repository's workflows.

  • What the runners a public repository trusts have reported of its workflows, as an appview has indexed it from the firehose.

  • What a repository's runners ran: every run of its workflows, and the workflows themselves.