Using --subgroups when there are no subgroups does not properly return data

[elboletaire]

I'm unable to get this working.. I've tried a lot of things, and I only get two errors:

• Error: could not resolve "false"
• Error parsing configuration

I installed the latest version using yarn, and I've gtt installed in yarn's default binary path. Using node version 6.11.3.

Here's my configuration file (located under ~/.gtt/config.yml):

url: https://gitlab.cirici.com/api/v4/
token: MY_PRIVATE_TOKEN

Using that file, I only get the error Error: could not resolve false.

If I create a .gtt.yml file in home with the following contents:

url: https://gitlab.cirici.com/api/v4/
token: MY_PRIVATE_TOKEN
extend: false

Then rises the error Error parsing configuration...

What am I doing wrong¿?

[elboletaire]

OFC I've tried copy-pasting the entire config file described in the readme, but I get the same behavior.

[kriskbx]

You need to specify a project. Either in your config:

project: "username/project-name"

... or on the command line.

gtt report "username/project-name"

I'm sorry that the error-message is not very helpful. I will work on this. Thanks for pointing this out. :)

[kriskbx]

Btw. you can specify groups or multiple projects/groups too!

[kriskbx]

If you get the error Error parsing configuration you probably have a syntax error in your config file. YAML can be hard sometimes, especially with spaces. You can use an online YAML parser that shows more verbose errors: https://yaml-online-parser.appspot.com

[kriskbx]

I just pushed 1.6.7 which features more verbose error messages (and preview gifs, yay!)
Feel free to reopen the issue if you still need help. :)

[elboletaire]

I'm sorry but I'm unable to get it working...

gtt --version
1.6.7

😢

[kriskbx]

Hmm. This looks like a connection problem. Unfortunately gtt doesn't check that separately. So I pushed a new version that introduces the option --check_token.
Please update to 1.6.8 and try again with the above option to enable token checking up front: gtt should throw an error when the connection to GitLab itself fails (because of a wrong url, token or access rights). So we can rule out that this is a permission problem.

[elboletaire]

Thanks! Now it says Invalid access token!. I've created a token from my /profile/personal_access_tokens page giving it api and read_user privileges and I'm administrator of this gitlab installation.

What can be wrong? 😕

[elboletaire]

Oh, wait! I've two factor auth enabled in gitlab... I should disable it, right?

[elboletaire]

Errr.... I don't know what I done but now it's working (without disabling the 2fa), so you can close this issue.

Again, thanks for your patience!

[kriskbx]

No worries, you're welcome!

2FA should not be a problem: the personal access token is a different authentification system. I actually had to create a new access token in the past after a GitLab updat. So maybe the most recent update did something weird and your token didn't work until you refreshed that page? Dunno, just guessing here. Glad it worked out for you in the end. :)