Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

actions/checkout@v4 - /api/v1/repos/administrator/runner1/tarball/master - Page not found 404 #32481

Closed
virtualdreams opened this issue Nov 12, 2024 · 5 comments · Fixed by #32572
Closed

actions/checkout@v4 - /api/v1/repos/administrator/runner1/tarball/master - Page not found 404 #32481

virtualdreams opened this issue Nov 12, 2024 · 5 comments · Fixed by #32572
Labels
issue/workaround it is or has a workaround topic/api Concerns mainly the API topic/gitea-actions related to the actions of Gitea type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@virtualdreams
Copy link

virtualdreams commented Nov 12, 2024 •
edited
Loading

Description

The action actions/checkout@v4 won't work if git not exists in docker container. The action tries to download from an invalid url. The url is also not available in /api/swagger.

Workflow

name: Runner1 Test Checkout
run-name: Runner1 Test Checkout
on: [push]

jobs:
  checkout:
    name: checkout
    runs-on: alpine
    defaults:
      run:
        shell: sh
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          ref: master

Output of act_runner in gitea

Deleting the contents of '/workspace/administrator/runner1'
The repository will be downloaded using the GitHub REST API
To create a local Git repository instead, add Git 2.18 or higher to the PATH
Downloading the archive
404 page not found

Error in log from gitea

GET /api/v1/repos/administrator/runner1/tarball/master for 172.19.0.2:58436, 404 Not Found in 5.7ms @ http/server.go:2188(GlobalNotFound)

If i try to download manually

curl http://gitea.example.org:3000/api/v1/repos/administrator/runner1/tarball/master
404 page not found

Repository is public.

Gitea Version

1.22.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

On host directly.

Database

MySQL/MariaDB
@Zettat123 Zettat123 added the topic/gitea-actions related to the actions of Gitea label Nov 12, 2024
@virtualdreams virtualdreams changed the title actions/checkout@v4 - /api/v1/administrator/runner1/tarball/master - Page not found 404 actions/checkout@v4 - /api/v1/repos/administrator/runner1/tarball/master - Page not found 404 Nov 12, 2024
@vcicmanec
Copy link

Facing the same issue, seems to be related to this
#29654

@lunny
Copy link
Member

lunny commented Nov 13, 2024 •
edited
Loading

Gitea doesn't support the API endpoint /api/v1/repos/<username>/<reponame>/tarball/<branch_name> yet.
ref: https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28#download-a-repository-archive-tar
ref: https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28#download-a-repository-archive-zip

@lunny lunny added type/proposal The new feature has not been accepted yet but needs to be discussed first. topic/api Concerns mainly the API and removed type/bug labels Nov 13, 2024
@Tockra
Copy link

Tockra commented Nov 18, 2024

I would be nice if the implementation of the endpoints will be occur in future. Currently I fixed this issue by adding the step:

      - name: Install git
        run: apt-get update && apt-get install -y git

But its a little bit annoying losing this 15 seconds in each job

@lunny lunny added the issue/workaround it is or has a workaround label Nov 18, 2024
@lunny
Copy link
Member

lunny commented Nov 18, 2024

You can install git in your docker container. So there will be no extra additional time.

@Tockra
Copy link

Tockra commented Nov 19, 2024 •
edited
Loading

You can install git in your docker container. So there will be no extra additional time.

But it is not the case, that I'm using a own docker image. I'm using public images from docker.hub which does not incldue git.
So I have to build my own image, upload it to my own registry, ensure the gitea runner is logged into that registry (which is not trivial) and then I spare the 15 seconds of the git installation.
I think its not a great deal.
It would be 1000% better just to fix that very basic checkout action (provide the missing endpoints).
I'm asking myself if I chose the wrong horse (gitea) when I see that this bug is known since beginning of 2024 and no fix is here yet.

@lunny lunny mentioned this issue Nov 20, 2024
Merged
@lunny lunny closed this as completed in 703be6b Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
issue/workaround it is or has a workaround topic/api Concerns mainly the API topic/gitea-actions related to the actions of Gitea type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add github compatible tarball download API endpoints lunny/gitea
5 participants
@lunny @Tockra @virtualdreams @vcicmanec @Zettat123