The error pull.source

user: the script can change it: the error says what happened in the experiment’s names, and what to write instead.

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

  • what happened: --link {…}: {…}; nothing was sent

  • what to do: 'mime pull --link -', then paste the link the record's page gives; or set {…} to it, then 'mime pull --link env'

• in mime/push/_client.py:

  • what happened: (built where it is given, so not read here)

  • what to do: pull from a service by its name, 'mime pull --from zenodo-sandbox <record>'

• in mime/push/_records.py:

  • what happened: an address at {…} carries an access key (its {…} parameter), which goes to a record's own service alone, and the DOI resolver is not one; nothing was sent

  • what to do: give the link as the record's page gives it, in quotes (a shell reads its ? and &): 'mime pull '<site>/records/<record>?{…}=...'', or 'mime pull --link -', which asks for it with no echo

• in mime/push/_records.py:

  • what happened: an address on {…}'s host carries an access key (its {…} parameter), and is not the share link {…}'s page gives, {…}: {…}; a link's key goes to its service's own host alone, so nothing was sent

  • what to do: give the link as the record's page gives it, in quotes (a shell reads its ? and &): 'mime pull '{…}'', or 'mime pull --link -', which asks for it with no echo

• in mime/push/_records.py:

  • what happened: {…}://{…}{…} carries an access key (its {…} parameter), and it is not the share link of a record on {…}, which is {…}; nothing was sent

  • what to do: give the link as the record's page gives it, in quotes (a shell reads its ? and &): 'mime pull '{…}'', or 'mime pull --link -', which asks for it with no echo

• in mime/push/_records.py:

  • what happened: {…} is a DOI on {…}, not on {…}: the same number names another record there

  • what to do: pull it from {…}, 'mime pull --from {…} {…}'

• in mime/push/_records.py:

  • what happened: {…} is not a record's number on {…}

  • what to do: give the number its page ends with, its page or its DOI, 'mime pull --from {…} 629525'

• in mime/push/_records.py:

  • what happened: a download of the record {…} outside {…}'s API, which pull never sends a token to

  • what to do: pull the record by its number, 'mime pull --from <service> <record>'

• in mime/saved/_pull.py:

  • what happened: {…}: {…}

  • what to do: give an https:// address, a DOI, or a file: 'mime pull <doi | url | file>'

• in mime/saved/_pull.py:

  • what happened: {…} is not a file on this machine, a DOI or an https:// address

  • what to do: give the bundle's DOI, its address, or its file: 'mime pull 10.5281/zenodo.1234567'

• in mime/saved/_pull.py:

  • what happened: a share link of the record {…} on {…} carries its own key, and is pulled without --signed-in or a share link of the record {…} on {…} carries its own key, and is pulled from {…}, not from {…}

  • what to do: pull the link alone, 'mime pull '<the link>''

• in mime/saved/_pull.py:

  • what happened: with --from or --signed-in, pull takes a record's number, and this is an address that carries an access key (its token parameter) and is no share link of either service; nothing was sent

  • what to do: pull the record by its number, 'mime pull --from <service> <record>', or the address alone

• in mime/saved/_pull.py:

  • what happened: --signed-in sends the token stored for the service --from names, and no --from is given

  • what to do: pull the record by its number from its service, 'mime pull --from zenodo <record> --signed-in'

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