-
Notifications
You must be signed in to change notification settings - Fork 107
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
Gitlab plugin fails with TypeError #168
Comments
It seems that you are not using a valid username:
You should provide an existing user in the config, for example:
Or omit it from the config altogether, then it would be detected from the email address. Does that help? |
Out of habit, I substituted he username in the config and output copied to this issue. When running, the config is correct, and the output reflects the use of the 'rkratky' username (regardless of whether I omit it and rely on the email address, or configure it explicitly using the |
I was able to reproduce a similar error by creating an access token with |
Honestly, I don't know what constitutes Unfortunately, not on GitLab. There, I have a token with 'API' access, but I'm still getting the TypeError. I tried with a freshly generated token and updated |
We should clearly specify the GitLab scope in the documentation: 4bcc705. So you get the |
No, when I remove it from Gitlab settings, it works. (It works with it for GitHub.) Before, it worked if there was no activity during the reported period. With the correct token, it works. |
The following configuration:
results in:
Tried with multiple different Gitlab instances, but the result is always the same.
When I comment out
ssl_verify = true
, then it appears to work, but only if there's no activity. If there is something to report, it fails with:My address on gitlab.com is
@gmail.com
, but notice that it fails already during the run with@redhat.com
.did version:
The text was updated successfully, but these errors were encountered: