microsoft / microsoft/azure-devops-python-api
"filter_contains" argument causes get_refs to find no matches
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
Hi,
I have a piece of code that uses get_refs with a prefix filter argument. I observed the results and then I put in filter_contains a character that I can see exists in all the refs returned from the first call to get_refs. The call with the filter_contains returns 0 refs.
refs = self._connection.clients_v5_1.get_git_client().get_refs(repository_id = repo_id,
project = project_id,
filter = prefix_filter,
peel_tags = True,
include_statuses = True,
latest_statuses_only = True,
top = 100,
continuation_token = continuation_token)
In this example, all relevant ref name field contain the character 'V'. The call:
refs = self._connection.clients_v5_1.get_git_client().get_refs(repository_id = repo_id,
project = project_id,
filter = prefix_filter,
peel_tags = True,
include_statuses = True,
latest_statuses_only = True,
top = 100,
continuation_token = continuation_token,
filter_contains = "V")
results in refs containing 0 results, and the call returns almost immediately, as opposed to taking several seconds in the first call.
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Python client's get_refs entry point and inspect how the filter and filter_contains arguments are sent. Reproduce the reported case with refs containing 'V', then verify that filter_contains returns those matching refs instead of an empty result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100