The error push.token

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

  • what happened: {…} does not accept the token (401: {…})

  • what to do: make a new personal access token on the service's site and store it, 'mime credentials set {…}'

• in mime/push/_draft.py:

  • what happened: no token for {…}: push uploads with the token of the account the draft belongs to; nothing was sent

  • what to do: make a personal access token with the scopes deposit:write and deposit:actions on the service's site and store it, 'mime credentials set {…}'

• in mime/push/_draft.py:

  • what happened: the tokens held for {…} and {…} are the same token, and a token is the token of one service's account: one of them is held under the wrong name; nothing was sent

  • what to do: make each on its own service's site and store it under that service's name, 'mime credentials set {…}' and 'mime credentials set {…}'

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