Make sure we correctly calculate that an account is collaborator in a gitlab namespace
sentry-io opened this issue · comments
Sentry Issue: PACKIT-SERVICE-3DB
Account rhdrjones has no write access nor is author of PR!
We are getting reports like these in the gitlab.com/redhat/centos-stream/src namespace even though the accounts are redhatters which totally have write access to the namespace (maybe we need to check parent namespaces as well?)
>>> import os
>>> from ogr import GitlabService
>>> s = GitlabService(token=os.getenv("GITLAB_TOKEN"))
>>> p = s.get_project(namespace="redhat/centos-stream/src", repo="qemu-kvm")
>>> p.can_merge_pr("rhdrjones")
True
I'll have a look if there is some update for python-gitlab or it's just flake, since I see only 1 occurence.
tl;dr our bot account cannot see all groups so can't determine the write access properly; we're reaching out to the infra teams handling gitlab.com/redhat
This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.
Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.
This is done in order to ensure that open issues are still relevant.
Thank you for your contribution! 🦄 🚀 🤖
(Note: issues labeled with pinned or EPIC are
never marked as stale.)
uhhhh, I have no idea if this is resolved or not, but my assumption it isn't :/
@TomasTomecek well, this can't be resolved on ogr's side, I think the latest update from this was that you reached out to infra team to do something about that, but haven't heard nor seen any link since then
This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.
Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.
This is done in order to ensure that open issues are still relevant.
Thank you for your contribution! 🦄 🚀 🤖
(Note: issues labeled with pinned or EPIC are
never marked as stale.)
@TomasTomecek let's keep closed? as it is out of our hands?