[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4098: CircleCI is Broken

[Tahoe-LAFS]

#4098: CircleCI is Broken
-------------------------+-----------------------
     Reporter:  meejah   |      Owner:
         Type:  task     |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by sajith):

 I received a response from CircleCI support. Basically a GitHub org admin
 will need to step in.

 {{{
 -------- Forwarded Message --------
 From: Martin (CircleCI)
 Subject: [CircleCI] Re: "fatal: Could not read from remote repository."
 Date: 08/22/2024 12:13:14 PM

 ##- Please type your reply above this line -##
 Your request (153696) has been updated. To add additional comments, reply
 to this email.
 Martin (CircleCI)
 Aug 22, 2024, 12:13 CDT

 Hello ,

 Thank you for reaching out to CircleCI Support. Based on the
 information provided, it seems like there might be an issue with the
 SSH keys or permissions since this behavior is happening on the
 checkout step.

 One possible reason could be that the checkout SSH key got
 removed. This can happen when changes are made to the developer
 accounts or organization settings on GitHub. Resetting webhooks,
 checkout keys, and deploy keys associated with the project can help
 ensure you're working with a known good setup going forward. You can
 follow the steps in this Support Center article
 <https://support.circleci.com/hc/en-us/articles/360021666393-How-to-
 manually-stop-building-by-removing-your-deploy-key-and-webhook-from-
 GitHub>
 to do so.

 Another possibility is that there might be expired tokens in the
 environment variables. CircleCI handles the auth for you when it
 creates the key and adds it to GitHub, so most of the time,
 git-related auth in the environment variables aren't necessary. If
 there are expired tokens, it could prevent CircleCI from checking out
 the code.

 Lastly, have any project admin please ensure that CircleCI is enabled
 in their GitHub organization's third-party app restrictions in their
 Organization Settings
 <https://support.circleci.com/hc/en-us/articles/360056873811-Your-access-
 to-a-project-from-CircleCI-was-revoked-by-GitHub>. You
 can read more about these restrictions in GitHub's Documentation
 <https://help.github.com/articles/about-oauth-app-access-restrictions/>.

 Please pass this information on to the project admin on GitHub so they
 can check these settings. If the issue persists, please let us know.

 Thank you,
 Martin
 Support Engineer @ CircleCI
 }}}

 In the meanwhile check-outs have resumed working.  I don't know if this
 happened because of something CircleCI did, or some random buttons I
 clicked on CircleCI, or someone else acting quietly.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4098#comment:15>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage