Error using CLI when processing Azure DevOps PR URLs that include spaces

[jamesweale]

Git provider

Azure

System Info

deployment type: CLI with Azure DevOps Repo

Bug details

I ran into issues when trying to use pr-agent with an Azure DevOps repo that contains a space in its url e.g. https://dev.azure.com/orgname/Dev%20Project/_git/repo_name/pullrequest/1234

I installed pr-agent using uv and configured following these instructions and ran it using cli.run_command with DefaultAzureCredential.

When I ran cli.run_command(pr_url, command), I received this error:

RuntimeError: asyncio.run() cannot be called from a running event loop

However, when I bypassed the CLI and called the AzureDevopsProvider directly using the same settings and PR URL, a different error appeared:

AzureDevOpsClientRequestError: Operation returned a 404 status code

After some testing, I found this happens when the Azure DevOps project name contains a space. Using the azure-devops library manually, I created a client and tested the get_pull_request_by_id method and managed to get it working only when the project is passed with a space rather than the %20 i.e. 'Dev Project' rather than 'Dev%20Project'.

Workaround

As a workaround, I cloned the repo locally and updated the _parse_pr_url static method to remove the %20 in the project and repository names using the unquote function from urllib. After applying this change, I was able to connect successfully and run the review command against the pull request and post the result as a comment.

Additional note

Just as a side note, when looking at other issues I noticed that the issue #740 raised a similar issue, but the fix was applied to the server webhook file but doesn’t cover this case in the AzureDevopsProvider class.

[qodo-merge-for-open-source]

💡 Auto-generated documentation-based answer:

Thanks for the detailed report. Two separate issues are involved:

1. asyncio.run() in an active event loop

• Cause: Calling cli.run_command() from an async context.
• Quick fix: Invoke the CLI as a process instead of inside an existing loop, e.g.:
  python -m pr_agent.cli --pr_url="https://dev.azure.com/org/Dev%20Project/_git/repo/pullrequest/1234" review
  Or, if you must call from async code, await the tool’s async entrypoints rather than wrapping cli.run_command() (which uses asyncio.run internally).

2. Azure DevOps URL with spaces (%20) returns 404

• Docs note that Azure DevOps provider is supported and requires setting:
  [config]
  git_provider="azure"
  and an [azure_devops] org URL in .secrets.toml.
• Your finding is correct: Azure DevOps REST calls expect the project “Dev Project” (space) rather than “Dev%20Project”. Decoding the project/repo parts before calling the API is needed.
• Workaround you used (urllib.parse.unquote on project/repo in URL parsing) is the right direction until an upstream fix lands.

Recommendation:

• Use the CLI form (python -m pr_agent.cli ...) to avoid the asyncio.run() error.
• Continue unquoting the project and repo segments in the AzureDevopsProvider URL parsing (similar to the webhook-side fix you referenced). Consider opening/adding details to the GitHub issue so the fix can be applied in the provider class.

If you share:

• The exact invocation context (sync vs async)
• Your [azure_devops] config (with org URL) and auth mode (PAT vs DefaultAzureCredential)
  we can suggest a precise code snippet for calling the provider without hitting asyncio.run(), and point to the correct place to decode names in the provider.

Relevant Sources:

• https://qodo-merge-docs.qodo.ai//installation/azure#azure-devops-from-cli
• https://qodo-merge-docs.qodo.ai//usage-guide/automations_and_usage#azure-devops-provider
• https://qodo-merge-docs.qodo.ai//installation/locally#i-get-an-error-when-running-the-docker-image-what-should-i-do