toolchain.artifact_write_failed

A file Jadpo writes for you, such as a record, couldn't be written, usually because it or its folder is read-only.

Area 14, Tools; not declinable; the next step is usually the human's.

Why Jadpo refuses it

Commands such as jadpo records update, jadpo api update, jadpo migrate new and jadpo build write files you commit or deploy. When the operating system refuses one, the command stops there and says which file and why, rather than carry on as if the project were up to date.

Jadpo won't change permissions for you: who may write in the project is a decision about your machine, not about the app.

What it looks like

The project's folder is read-only, and access.jadpo_record, the record of who can do what, has to be written again:

rm access.jadpo_recordchmod a-w .jadpo records update

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides who may write in the project.

How to fix it

If the folder or the file should be writable, let yourself write to it, then run the command again:

chmod u+w . access.jadpo_recordjadpo records update

The record is written, ready to commit with the code.

If a tool keeps the files read-only until you open them for editing, open the record for editing with that tool, then run the command again:

jadpo records update

The record is written, and the tool shows it as changed, ready to commit with the code.

Related

• jadpo records
• Record files
• The build/ folder