The error push.rejected#
user: the script can change it: the error says what happened in the experiment’s names, and what to write instead. internal: a check on MIME’s own construction, which no supported script should reach: a MIME defect, to report with the file the error names; or an error MIME raised with no code yet (error.uncoded), keeping its own class, to report so that it gets one.
Where MIME gives it, with what its message says happened and what its action says to do ({…} is filled in from the experiment):
in
mime/push/_client.py:what happened:
{…}: {…}what to do:
correct it in sharing.yaml, then 'mime push <folder> --to {…}', which writes the draft's metadata again
in
mime/push/_client.py:what happened:
{…}: {…}what to do:
correct the licence or terms where the experiment is built, exp.licence(...) or Terms(...), save it again, built.save(folder), then 'mime push <folder> --to {…}'
in
mime/push/_client.py:what happened:
{…}, in a field MIME builds, not one you write: {…}. This is MIME's defect, not yourswhat to do:
report it with this message
in
mime/push/_client.py:what happened:
{…}, naming no field: {…}. What it refused is what MIME built, so this is MIME's defect, not yourswhat to do:
report it with this message
Reading an error and reaching its full traceback: reading an error. Every code: the index.