The error pull.record

environment: something the run needs is missing or different where it runs (a package, a file, a device, the network): the error names what to install, fetch or attach.

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/_records.py:

  • what happened: {…} could not be read at {…}: {…}

  • what to do: check the network, then 'mime pull --from <service> <record>' again

• in mime/push/_records.py:

  • what happened: {…} holds no published {…} (404)

  • what to do: check the record's number on its page, {…}/records/<record> (a draft is not public until it is published), then 'mime pull --from {…} <record>'

• in mime/push/_records.py:

  • what happened: {…} answered {…} with {…}, not the record's JSON

  • what to do: run the same command again later, 'mime pull --from <service> <record>'

• in mime/push/_records.py:

  • what happened: the record {…} on {…} is a draft, which only its owner reads

  • what to do: publish it, 'mime push <folder> --to {…} --publish', then pull it

• in mime/push/_records.py:

  • what happened: the record {…} on {…} holds {…} bundle files (its files: {…})

  • what to do: pull a record 'mime push' made, which holds one bundle

• in mime/push/_records.py:

  • what happened: the record {…} on {…} states no md5 and size for {…}

  • what to do: run the same command again later, 'mime pull --from <service> <record>'

• in mime/push/_records.py:

  • what happened: the bundle of the record {…} on {…} could not be downloaded: {…}

  • what to do: check the network, then 'mime pull --from <service> <record>' again

• in mime/push/_records.py:

  • what happened: {…} answered the bundle of the record {…} with {…}

  • what to do: run the same command again later, 'mime pull --from <service> <record>'

• in mime/push/_records.py:

  • what happened: {…} sent the bundle of the record {…} to another host with the share link's key in its address, which pull sends to the service's own host alone; nothing was asked there

  • what to do: ask the record's owner for the bundle file, then 'mime pull <the .mimebundle file>'

• in mime/push/_records.py:

  • what happened: the bundle of the record {…} could not be downloaded from where {…} stores it: {…}

  • what to do: check the network, then 'mime pull --from <service> <record>' again

• in mime/push/_records.py:

  • what happened: {…} redirected the bundle of the record {…} within its API twice

  • what to do: run the same command again later, 'mime pull --from <service> <record>'

• in mime/saved/_pull.py:

  • what happened: the record doi:{…} could not be read: {…}

  • what to do: check the DOI and the network, then 'mime pull <doi>' again

• in mime/saved/_pull.py:

  • what happened: the record doi:{…} lists {…} bundle files (its files: {…})

  • what to do: name the one to pull: 'mime pull doi:{…}/<file>{…}'

Reading an error and reaching its full traceback: reading an error. Every code: the index.