Run-extractor pipeline was failing with (A potentially dangerous Request.Path value was detected from the client) while creating the PR about apiops

[waelkdouh]

Does the extractor work fine if you run it locally on your machine?

[Nag0546]

Thanks for quick response…. Yes extractor is working fine and able to see all templates as well in folder only PR task is failing with that error. One more thing is we trained same commands in azure cloud shell as well there also we are getting same error.  Thanks & Regards Nageswara Rao

…

On Mon, 30 May 2022 at 8:17 PM, Wael Kdouh ***@***.***> wrote: Does the extractor work fine if you run it locally on your machine? — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJTHF6BWZSLBYHGQMJCY7ITVMTIIBANCNFSM5XKY3TPQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Nag0546]

Please find the attached link for pipeline error screenshot.

[waelkdouh]

I know the scripts work for everyone else. So I am wondering if there is something specific within your azure devops environment.

[soibam]

Hi, I am facing the same exact issue while running the extractor pipeline in azure devops

And this is the place where the code is breaking

[waelkdouh]

Can you try getting another PAT token? It could be something in the PAT token.

[soibam]

Can you try getting another PAT token? It could be something in the PAT token.

Sorry for the confusion I have corrected the screenshot above and you can see the issue is while trying to get the clone url.

[waelkdouh]

Couldn't reproduce on my side. Sounds like an issue that might be related to your azure devops environment.