toolchain.source_read_failed

A .jadpo file in the project couldn't be read, because it isn't UTF-8 text or you aren't allowed to read it.

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

Why Jadpo refuses it

Jadpo checks the whole project at once, since a declaration in one file can be used in any other. A file it can't read could hold any of them, so checking without it would report errors that aren't there, or miss ones that are. It names the file and why reading failed, and checks nothing else until it can.

Source is read as UTF-8 text. Jadpo won't convert a file saved in another encoding, since doing so means guessing which one it was.

What it looks like

An editor saved app.jadpo as Latin-1, so the é in its comment is one byte that isn't UTF-8:

iconv -f UTF-8 -t LATIN1 app.jadpo > app.latin1mv app.latin1 app.jadpojadpo check

(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 how a file you saved is read.

A file you aren't allowed to read is refused the same way, with Permission denied as the reason.

How to fix it

If you know the encoding it was saved in, convert it to UTF-8, here from Latin-1:

iconv -f LATIN1 -t UTF-8 app.jadpo > app.utf8mv app.utf8 app.jadpojadpo check

The file reads as it was typed, and the whole project is checked again. An editor's "save with encoding" does the same.

If you aren't allowed to read it, make it readable:

chmod u+r app.jadpojadpo check

jadpo check reads the file and checks the project with it.

Related

• jadpo check
• Source files