-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Attempt to enable a second Bitbucket repo results in UNIQUE constraint failed: orgs.name #2793
Comments
Also, here's the sqlite dump of the orgs table:
As you can see, the name field in the above record is the empty string. |
Found a workaround: drop the index.
I now end up with these two rows:
|
So it complains as the names of your orgs are somehow |
Hi, @anbraten! Confirming that both the workspace name and the workspace ID in Bitbucket are populated with strings in the pattern [A-Za-z]+. |
Workaround not helpful- if you restart the service, it will be caught in a crashloop with:
|
Component
server
Describe the bug
Hi! I am attempting to build and run a new installation of woodpecker and encountered the following issue when adding repositories:
Steps to reproduce
Launch a woodpecker server (v1.0.5) and agent instance using the Bitbucket repo client.
From the repositories tab, choose a repo and click Enable.
Again, from the repositories tab, choose a second repo and click Enable.
Expected behavior
The repository is enabled successfully.
Actual behavior
The bottom right of the screen contains the following error highlighted in red:
UNIQUE constraint failed: orgs.name
, which is a SQLite error.System Info
The text was updated successfully, but these errors were encountered: