-
-
Notifications
You must be signed in to change notification settings - Fork 389
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.
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
Adding Repository Fails #4782
Comments
Can you check the logs for the lines before the stacktrace? |
Hello, I'm facing the same issue like above but with Gitea. Concerning your question @qwerty287 there is not much more before the error.
|
Using the v3-tag for the images solves this issue. Why am getting the deprecated v2.8.3 with the latest tag anyway? |
I mean before the panic itself. Is there anything? Is that a new org that never had a repo before or does it exist already?
What do you mean? 3.0.1 is the latest version. |
@nyaaaaaaatalie can you verify that this is fixed in 3.0.1? |
Can confirm. Good to close. Apologies on my part for not checking it was up to date. |
Component
server
Describe the bug
I am using the Docker container for Woodpecker connected to Forgejo. The Forgejo server uses an external OIDC IDP for authentication. When I add a repo, sometimes I will get the message "An unknown error has occured". In the Docker logs, I see the attached log messages and traceback. Interestingly. it seems that I can add projects that are under my user namespace; but not ones that are under an organization (despite me owning the org in Forgejo).
Steps to reproduce
Expected behavior
When I click "Enable" on a repository I expect it to enable with success.
System Info
Additional context
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: