unikraft / pykraft

Python library for configuring and building unikernels
Other
177 stars 42 forks source link

kraft list update 404 #104

Closed aiaoyang closed 2 years ago

aiaoyang commented 2 years ago

Describe the bug A clear and concise description of what the bug is. when execute kraft -v list update, raise [CRITICAL] 404 {"message": "Not Found", "documentation_url": "https://docs.github.com/rest"} To Reproduce run kraft list update Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior update success A clear and concise description of what you expected to happen.

Screenshots

image

Desktop (please complete the following information):

Additional context github token have been create with repo:public_repo permission

StefanJum commented 2 years ago

Hi, please make sure that the token ONLY has the repo:public_repo permissions. Also make sure to export it as UK_KRAFT_GITHUB_TOKEN before you run kraft list update, or use the command UK_KRAFT_GITHUB_TOKEN=<your_GitHub_token_here> kraft list update.

aiaoyang commented 2 years ago

Hi, please make sure that the token ONLY has the repo:public_repo permissions. Also make sure to export it as UK_KRAFT_GITHUB_TOKEN before you run kraft list update, or use the command UK_KRAFT_GITHUB_TOKEN=<your_GitHub_token_here> kraft list update.

yes, Im sure there is only repo:public_repo permission and export UK_KRAFT_GITHUB_TOKEN has been set before I execute the kraft list update command. when token is not set, the response show this below

image
ppttech commented 2 years ago

I am experiencing the same issue. I set the env var before running kraft list update (of course) and only selected the public_repo option when creating the token.

amirkmzh commented 2 years ago

I have faced the same error, And I have exactly followed the tutorial.

gabrielmocanu commented 2 years ago

@amirkmzh @ppttech @aiaoyang Can you check again? Please make sure that you re-install kraft after git pull.

ppttech commented 2 years ago

@gabrielmocanu For me it is fixed now, at least kraft list update doesn't throw this error anymore. Thanks!