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
Group share with another group fails on a second run #236
Comments
Debug logs show:
Notice the register. Looks like I'll try to make a local change to see if works any better. |
Hi, I wasn't able to reproduce this, but I agree that it is much better to use path than name. Were any of your groups subgroups? I've created a PR #237 which adds support for subgroups. Thanks, |
Actually, I have managed to reproduce it now. Hopefully I'll have a fix soon 😄 |
I've confirmed that this is caused when you have a name that has non-url safe character in it (e.g. a space replaced by a hyphen in the path). This is fixed by #237. Cheers, |
@andrewjw you're pure speed! |
Got the same issue in 2.2.0:
The config snippet: projects_and_groups:
# settings for ALL projects in 'scm-test-zone' group
"ei/scm/scm-test-zone/*":
group_shared_with:
ei/reviewers/helm:
group_access_level: 30 |
Do you also observe the issue on the second run only, @aleung ? If so, then I was not able to reproduce it easily yet, see commit above... |
@gdubicki I tried it just now. It failed on the second run only. The first time the group wasn't shared so it won't fail.
|
Can you please check this again with v2.8.0 released a moment ago, @aleung ? The implementation for sharing group with groups has changed a bit there. |
I ran into this issue and found the problem was that I was using the Group name rather than the path. The name was something like "group-Name" and had capitals while the path was more like "group-name" and did not. GitLabForm should fail on the first run if sharing a group by name rather than path, but it can be easily mitigated by always using the path. |
For whatever it's worth: I get the error with version 3.8.0 on the second run, even if I use paths. I have
The first run succeeds, the second run fails to do any updates to
What I mean with "any updates" is that if it has multiple another-sub-group-1, another-sub-group-2 it will fail. Also the enforcement fails, i.e., superflous shares aren't deleted (logically). |
Maybe this will be fixed when #633 has been done. Would anyone be able to help with that? |
The bug description
There is an awesome new feature to add a group as a member to another group.
Added in #233 by fantastic @andrewjw
Unfortunately it fails to recognise existing shares (created manually or by GitLabForm itself).
Steps to reproduce:
Anonymized error:
There is a check in code that should end up with
"Nothing to change for group '%s' - same config now as to set.",
, but it seems to be not working for some reason.GitLabForm version
🏗 GitLabForm version: 2.1.0 = the latest stable 😊
GitLab version
14.0.1
The text was updated successfully, but these errors were encountered: