Skip to content

A lot of HTTP 422 errors are happening in the repository plugin with the latest code #794

@decyjphr

Description

@decyjphr
Collaborator

Problem Description

What is actually happening

A lot of HTTP 422 errors are happening in the repository plugin with the latest code

What is the expected behavior

No errors should be happening. I tested with an older version and they do throw hose errors

Error output, if available

Error {"name":"HttpError","status":422,"response":{"url":"[https://api.github.com/repos/decyjphr-emu/rails-2","status":422,"headers":{"access-control-allow-origin":"*","access-control-expose-headers":"ETag](https://api.github.com/repos/decyjphr-emu/rails-2","status":422,"headers":%7B"access-control-allow-origin":"*","access-control-expose-headers":"ETag), Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset","content-length":"245","content-security-policy":"default-src 'none'","content-type":"application/json; charset=utf-8","date":"Sun, 23 Mar 2025 02:18:06 GMT","referrer-policy":"origin-when-cross-origin, strict-origin-when-cross-origin","server":"github.com","strict-transport-security":"max-age=31536000; includeSubdomains; preload","vary":"Accept-Encoding, Accept, X-Requested-With","x-accepted-github-permissions":"administration=write","x-content-type-options":"nosniff","x-frame-options":"deny","x-github-api-version-selected":"2022-11-28","x-github-media-type":"github.v3; format=json","x-github-request-id":"51B0:25743B:B098FB:163D0EF:67DF6F5D","x-ratelimit-limit":"15000","x-ratelimit-remaining":"14831","x-ratelimit-reset":"1742699705","x-ratelimit-resource":"core","x-ratelimit-used":"169","x-xss-protection":"0"},"data":{"message":"Validation Failed","errors":[{"resource":"Repository","code":"custom","field":"name","message":"name already exists on this account"}],"

Context

Are you using the hosted instance of probot/settings or running your own?

local

If running your own instance, are you using it with github.com or GitHub Enterprise?

dotcom

Version of probot/settings

main-enterprise

Version of GitHub Enterprise

Activity

JTP3XP

JTP3XP commented on Apr 4, 2025

@JTP3XP

I am also seeing this error - I'm running via a GitHub Action and safe-settings seems to get through a couple repositories and then tries to rename the rest to an existing repo name.

decyjphr

decyjphr commented on Apr 4, 2025

@decyjphr
CollaboratorAuthor

I went back to a known working version and started applying changes. i looks like the problem is in the settings.js and the changes introduced by PR 692 causes the 422 errors.

decyjphr

decyjphr commented on Apr 4, 2025

@decyjphr
CollaboratorAuthor

I have a version of settings.js that does not have the changes for Archive plugin and it seems to work. So I will push that out this week and we can go back to troubleshooting the archive code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @JTP3XP@decyjphr

      Issue actions

        A lot of HTTP 422 errors are happening in the repository plugin with the latest code · Issue #794 · github/safe-settings