request.blobs_missing

The runner does not hold some files sent by hash


Type	`https://mthds.ai/errors/request.blobs_missing`
Family	`request`: The HTTP request itself, before any run.
Domain	`input`: the caller acts, by changing the request or its inputs
Retry	`no`: repeating the operation fails the same way
HTTP status	`422`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

A hash entry of the request's files names bytes this runner does not hold, or the runner keeps no blob store at all, so it cannot assemble the method's tree. This is the protocol's own refusal of hash entries.

What to do

Read params.missing_blobs. To a runner whose GET /version declares blob_store: true, upload each listed blob as POST /blobs/missing says; to any other runner, send each listed file inline. Then send the request again.

Next steps

A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the caller, and the second for any other reader.

Reader	Kind	Detail
The domain's actor	`change_input`	Upload each listed blob, or send its file inline if this runner keeps no blob store, then send the request again.
Any other reader	`change_input`	Pass this to the caller, who must upload each listed blob, or send its file inline if this runner keeps no blob store.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

This runner does not hold a file the request sends by hash.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`missing_blobs`	list of `sha256`	Each hash of the request that the runner does not hold, in lowercase hexadecimal.