NoneType Error for Same Tgt Repo after changing PAT

[tragulum]

Hey everyone, not sure if this rises to the level of an issue so, I'm throwing it here but can move it if need be. I ran gato against a target repo with a 3rd party PAT (i.e. personal one) and it worked fine for enumeration. I then used my work PAT for my work (classic PAT like before) GH account and when i try to enumerate, it throws a NoneType error complaining about it not being subscriptable. Obviously I have more perms with my work PAT than the personal one. Anyone else seen this happen?

[AdnaneKhan]

Hey everyone, not sure if this rises to the level of an issue so, I'm throwing it here but can move it if need be. I ran gato against a target repo with a 3rd party PAT (i.e. personal one) and it worked fine for enumeration. I then used my work PAT for my work (classic PAT like before) GH account and when i try to enumerate, it throws a NoneType error complaining about it not being subscriptable. Obviously I have more perms with my work PAT than the personal one. Anyone else seen this happen?

Can you share the specific line in src where the stack trace came from? This was just in single repo enum mode, correct?

If you see a stack trace, it's most likely a bug and, if anything, an opportunity for me to add some better checks, so feel free to make an issue with details. My gut feeling is that it has to do with SAML permissions (if you have a work PAT that is not SAML authenticated to a work org, but your account has access to it, it will get a 400 error even if the repo is public and the bug might be related to Gato not properly handling that case).