client.write_failed
A local file could not be written
| Type | https://mthds.ai/errors/client.write_failed |
| Family | client: What a client detects itself, and never receives as a response body. |
| Domain | input: the caller acts, by changing the request or its inputs |
| Retry | no: repeating the operation fails the same way |
| HTTP status | none (client) |
| Raised as | an error a client detects itself, never received from a runner |
What it means
The client could not write a file or a directory it was asked to produce.
What to do
Check the directory's permissions and the free space, or write somewhere else.
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 | fix_configuration |
Make '{path}' writable, or choose another place to write, then try again. |
| Any other reader | fix_configuration |
Make '{path}' writable, or choose another place to write, then try again. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The client could not write '
{path}' (reason:{reason}).
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
path |
caller_text |
The file or the directory. |
reason |
identifier |
Why it could not be written. |
See also
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry