search

actions / checkout

Action for checking out a repo
https://github.com/features/actions
MIT License
5.93k stars 1.75k forks source link

repository not found #254

Closed DgRosa closed 4 years ago

DgRosa commented 4 years ago

_[edited by @ericsciple] Sorry for the disruption. There is an active incident right now that is causing the GITHUBTOKEN to not have permission to checkout private repos.

Everything was working fine until all of the sudden this error started to popup and I have no idea why. Can it be a GitHub service issue or maybe a recent release that introduced a bug. It's a private repository I don't know if that can help debug the issue.

Workflow stack

/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +7f692a64151c6ae3be4518df16d88b891eb76c1b:refs/remotes/origin/master
  remote: Repository not found.
  ##[error]fatal: repository 'https://github.com/DgRosa/likacrm/' not found
  The process '/usr/bin/git' failed with exit code 128
ryanmiriyagalla commented 4 years ago

+1 on this. Github actions suddenly started giving this error. "Investigating - We are investigating an increase in errors on GitHub.com." I think this is due an error in github. Check https://www.githubstatus.com/

bigfootjon commented 4 years ago

I think it's something to do with private repos? I just reran some public repo actions and they worked correctly, but my private repos are failing every time.

dcarlstedt commented 4 years ago

I am also having this exact same issue. It started appearing somewhere in the last hour to our private repos.

sergeh commented 4 years ago

+1 also just started to happen on our private repos

mcbanderson commented 4 years ago

Happening on my private repos as well, for both v1 and v2.

Edit: Looks like GitHub is experiencing some service degradation, so this could be a GitHub issue and not an issue with this action.

faizanakram99 commented 4 years ago

Same, was about to open an issue.

Didn't know whether it is related to this repository or to GitHub

brettpalmberg commented 4 years ago

+1 . Same issue with GitHub Actions and private repos.

Albinzr commented 4 years ago

Same issue all the build process is stuck for me

dianhsu commented 4 years ago

Oops....

patrickk commented 4 years ago

+1, same here. Repo exists.

Albinzr commented 4 years ago

Are the any alternatives for checkout that can be used as fallback

Andrew-Kulpa commented 4 years ago

I'm experiencing this issue too! 👍

belalessandro commented 4 years ago

Same for me

pinkstrings commented 4 years ago

Anyone know if this is an issue with Github itself, or specific to the code in this action?

ilgooz commented 4 years ago

Anyone know if this is an issue with Github itself, or specific to the code in this action?

Probably due to an issue with Github APIs. We are using a fixed version of checkout which is @v2 and still experiencing this issue.

@ericsciple can you please report this issue to the team?

I got more news, the status page is yellow, there seems to be an incident ATM. See: https://www.githubstatus.com/

cfbao commented 4 years ago

Anyone know if this is an issue with Github itself, or specific to the code in this action?

Pretty sure it has nothing to do with the checkout action. The latest code change is yesterday, but it was running fine this morning.

veich commented 4 years ago

@GitHub Team - that's why you don't do deployments on Friday :grin:

EDIT: November 27th 2020 - repeat error & they did it again on Friday :facepalm: :joy:

handhead-dev commented 4 years ago

+1

ericsciple commented 4 years ago

@ilgooz there is an ongoing investigation - it's known. Not an issue w/ this repo as you mentioned.

ivandimitrovSC commented 4 years ago

Thanks for this issue! I literally merged our first workflow 90 minutes ago and have been debugging the broken CI ever since. Knowing it's service degradation is of some relief.

AnthonyKinson commented 4 years ago

+1 same thing just started happening in our org private repos

PrinsFrank commented 4 years ago

Only affects our private repos, public ones still work fine.

weihao commented 4 years ago

Adding logs

  remote: Repository not found.
  ##[error]fatal: repository 'https://github.com/user/repository/' not found
  The process '/usr/bin/git' failed with exit code 128
finnkauski commented 4 years ago

Same here. Issue with private repo deployment. Spent like and hour figuring it out. Feel like such an idiot not having a look here first!

batok commented 4 years ago

When actions/checkout runs fetches the master version of this repo? I mean github tries to fetch the most recent version?

fclaussen commented 4 years ago

When actions/checkout runs fetches the master version of this repo? I mean github tries to fetch the most recent version?

I had @v1 on mine and switched to @master when I saw the problem happening but no luck. I think it's related to the current github situation. https://www.githubstatus.com/

mukeshydv commented 4 years ago

+1 happening on my private repo too.

emilyzhang commented 4 years ago

+1 same

ericsciple commented 4 years ago

@fclaussen yes it's due to the incident. I edited the issue description now so folks dont have to scroll. Sorry about the disruption.

forensicmike commented 4 years ago

+1 same, private repo

Comver commented 4 years ago

+1 same, private repo

techjacker commented 4 years ago

I'm getting this too

anderstofte-zz commented 4 years ago

I thought I messed up some configuration files. "Glad" to see I'm not the only one having issues.

gnumoksha commented 4 years ago

+1 same, private repo

Durisvk commented 4 years ago

+1 same here

C0ZEN commented 4 years ago

Please use emojis to react and add comments only to provide new information. Most of us receive a tons of emails due to the subscribe.

benaubin commented 4 years ago

Not sure if it's related, but I'm starting to get a bunch of sporadic 500 errors while browsing GitHub (unless in incognito).

peaceiris commented 4 years ago

Please use emojis to react and add comments only to provide new information. Most of us receive a tons of emails due to the subscribe.

We can start to subscribe to the issue with this button without adding a comment.

Screen Shot 2020-05-23 at 5 23 35
DgRosa commented 4 years ago

Seems to be working now 😄

DgRosa commented 4 years ago

You're right, not working again...

Ameen-Alam commented 4 years ago

issue closed

scottliu1234 commented 4 years ago

@DgRosa Can we re-open this issue? Still failing.

elliothershberg commented 4 years ago

Also experiencing this issue.

tomp21 commented 4 years ago

Same problem.

damntrecky commented 4 years ago

Still experiencing issue. Linking my duplicate ticket here -> https://github.com/actions/checkout/issues/256

rhussmann commented 4 years ago

Seems to be working for me, now.

brickstar commented 4 years ago

Seems to be working for me now as well.

NZSmartie commented 4 years ago

I'm having a similar issue still but with the .wiki repository

Note that the first checkout succeeds, but the second checkout of the same URL with the .wiki suffix fails

2020-05-23T03:04:24.8524613Z ##[group]Run actions/checkout@v2
2020-05-23T03:04:24.8524869Z with:
2020-05-23T03:04:24.8524978Z   path: ./app
2020-05-23T03:04:24.8525071Z   repository: NZSmartie/SmartBikeTracker
2020-05-23T03:04:24.8525336Z   token: ***
2020-05-23T03:04:24.8525441Z   ssh-strict: true
2020-05-23T03:04:24.8525542Z   persist-credentials: true
2020-05-23T03:04:24.8525628Z   clean: true
2020-05-23T03:04:24.8525729Z   fetch-depth: 1
2020-05-23T03:04:24.8525829Z   lfs: false
2020-05-23T03:04:24.8525929Z   submodules: false
2020-05-23T03:04:24.8526016Z ##[endgroup]
2020-05-23T03:04:24.8541775Z ##[command]/usr/bin/docker exec  255e539ad105b12678c7e0b14ccf4e4f7c37b020a5dbf056c54770703d6ad812 sh -c "cat /etc/*release | grep ^ID"
2020-05-23T03:04:25.8580490Z Syncing repository: NZSmartie/SmartBikeTracker
2020-05-23T03:04:25.8595776Z ##[group]Getting Git version info
2020-05-23T03:04:25.8596439Z Working directory is '/__w/SmartBikeTracker/SmartBikeTracker/app'
2020-05-23T03:04:25.8678016Z [command]/usr/bin/git version
2020-05-23T03:04:25.8805018Z git version 2.17.1
2020-05-23T03:04:25.8827252Z ##[endgroup]
2020-05-23T03:04:25.8827412Z The repository will be downloaded using the GitHub REST API
2020-05-23T03:04:25.8827567Z To create a local Git repository instead, add Git 2.18 or higher to the PATH
2020-05-23T03:04:25.8831675Z Downloading the archive
2020-05-23T03:04:26.3977827Z Writing archive to disk
2020-05-23T03:04:26.4009101Z Extracting the archive
2020-05-23T03:04:26.4010373Z [command]/bin/tar xz -C /__w/SmartBikeTracker/SmartBikeTracker/app/a05210f3-f7b7-4fdb-92cd-158611bbf920 -f /__w/SmartBikeTracker/SmartBikeTracker/app/a05210f3-f7b7-4fdb-92cd-158611bbf920.tar.gz
2020-05-23T03:04:26.4162355Z Resolved version NZSmartie-SmartBikeTracker-a3fe4e81913cced9e2557860092d699dd36b0395
2020-05-23T03:04:26.5287695Z ##[group]Run actions/checkout@v2
2020-05-23T03:04:26.5287826Z with:
2020-05-23T03:04:26.5287929Z   repository: NZSmartie/SmartBikeTracker.wiki
2020-05-23T03:04:26.5288042Z   path: ./wiki
2020-05-23T03:04:26.5288290Z   token: ***
2020-05-23T03:04:26.5288398Z   ssh-strict: true
2020-05-23T03:04:26.5288500Z   persist-credentials: true
2020-05-23T03:04:26.5288589Z   clean: true
2020-05-23T03:04:26.5288691Z   fetch-depth: 1
2020-05-23T03:04:26.5288804Z   lfs: false
2020-05-23T03:04:26.5288905Z   submodules: false
2020-05-23T03:04:26.5288990Z ##[endgroup]
2020-05-23T03:04:26.5291552Z ##[command]/usr/bin/docker exec  255e539ad105b12678c7e0b14ccf4e4f7c37b020a5dbf056c54770703d6ad812 sh -c "cat /etc/*release | grep ^ID"
2020-05-23T03:04:27.3148323Z Syncing repository: NZSmartie/SmartBikeTracker.wiki
2020-05-23T03:04:27.3268363Z ##[group]Getting Git version info
2020-05-23T03:04:27.3293844Z Working directory is '/__w/SmartBikeTracker/SmartBikeTracker/wiki'
2020-05-23T03:04:27.3295144Z [command]/usr/bin/git version
2020-05-23T03:04:27.3384113Z git version 2.17.1
2020-05-23T03:04:27.3386913Z ##[endgroup]
2020-05-23T03:04:27.3387074Z The repository will be downloaded using the GitHub REST API
2020-05-23T03:04:27.3387213Z To create a local Git repository instead, add Git 2.18 or higher to the PATH
2020-05-23T03:04:27.3387364Z Downloading the archive
2020-05-23T03:04:27.4936199Z Not Found
2020-05-23T03:04:27.4937414Z Waiting 17 seconds before trying again
2020-05-23T03:04:44.5045197Z Downloading the archive
2020-05-23T03:04:44.6033207Z Not Found
2020-05-23T03:04:44.6037637Z Waiting 10 seconds before trying again
2020-05-23T03:04:54.6052725Z Downloading the archive
2020-05-23T03:04:54.6969308Z ##[error]Not Found
NZSmartie commented 4 years ago

It's still unresolved, the action still fails. I'm guessing no one else is performing a checkout on their wiki?

my workflow looks like the following:

name: Build
on:
  push:

jobs:
  build:
    runs-on: ubuntu-latest

    container:
      image: zephyrprojectrtos/zephyr-build:latest # container image is based on ubuntu 18.04
      options: --user root # override default user to resolve permission issues.

    steps:
      - name: Clone repository
        uses: actions/checkout@v2
        with:
          path: ./app
      - name: Also clone wiki # work around for West or Github Checkout Action limitation of private repos
        uses: actions/checkout@v2
        with:
          repository: ${{ github.repository }}.wiki
          path: ./wiki

CC: @ericsciple

ericsciple commented 4 years ago

@NZSmartie you may need to use a PAT or deploy key or SSH key.

The default token - i.e. ${{ github.token}} - doesn't have access to other private repos.

Hope that helps. Let's track in a separate issue if not. The checkout action hasn't changed, but could be a server side change if suddenly different behavior.