Azure DevOps - Unescaped Characters

[ghost]

When running this script on ADO, we get the following errors.

Job -yu5c341lgdj failed: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
Retrying job -yu5c341lgdj in 25ms!
Job -yu5c341lgdj failed: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
snyk:azure-devops-count Failed to retrieve repo list from Azure Devops.
snyk:azure-devops-count TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters +0ms
Failed to retrieve repo list from Azure Devops. Try running with DEBUG=snyk* snyk-contributor
snyk:azure-devops-count Fetching single repo contributor from Azure Devops. Project d38f51da-cd00-4a89-9721-ef5b5a5a500c - Repo

[IlanTSnyk]

Hi @pepsico-bn ,
Thank you for the feedback.
Can you please advise on the exact usage of the tool and the specific command flags used? (for example : did you run the command with the --projectKeys and the --repo flags?, Did you give a value for both the flags?)
Please check that the values given to the command do not contain any spaces.
If the the --repo flag was set, can you please advise if the repo name has any special characters?
Last thing : if the --repo flag was not set, did the script run for a while and then got "stuck" or did stop on the first try?
Thank you.

[ghost]

Hello, I used this command when I received the error listed.

I'm using a Mac running 11.6.1. I did not use either the --projectKeys or --repo flags. I checked the repo that seemed to cause the error, but could not find any characters that might lead to this error. It is possible that the error was actually from a different repo and was never listed in the logs.

The command I used:
./snyk-scm-contributors-count azure-devops --token abcdefg --org myOrg

[IlanTSnyk]

@pepsico-bn,
Thank you for the update.
Am I wrong to assume that you are a Snyk customer?
If you are, contact your CSM at Snyk and we can have a debugging session to figure out the issue, if that's ok by you.
Otherwise, I would check one repo up and one repo down the output of the command for the repo names and run a few dedicated commands to those specific repos by adding the --projectKeys and the --repo parameters to see if indeed the issue repeats itself.
Please let me know how you'd like to proceed.
Thanks.