The error pull.restricted

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

  • what happened: {…} keeps {…} back from the share link's key ({…}): the link was revoked or has expired, or the records API does not take a link's key as pull sends it (as its {…} parameter, a guess until a sandbox session measures it)

  • what to do: ask the record's owner for a new link; or, if it is shared with your account, 'mime pull --from {…} {…} --signed-in'

• in mime/push/_records.py:

  • what happened: {…} keeps {…} back from the token stored for it ({…}): it is a draft, or it is not shared with that token's account, or the token lacks a scope reading it needs

  • what to do: see whose token it is, 'mime credentials status {…}'; ask the record's owner to share it with that account, or for a share link, 'mime pull --link -', which asks for it with no echo; or download its bundle from its page signed in, {…}, then 'mime pull <the .mimebundle file>'

• in mime/push/_records.py:

  • what happened: {…} keeps {…} from anyone it is not shared with ({…}): {…}, and pull reads with no token unless asked

  • what to do: {…}; or download its bundle from its page signed in, {…}, then 'mime pull <the .mimebundle file>'; a share link, 'mime pull --link -', which asks for it with no echo; a draft, publish it first; otherwise ask its owner for access

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