New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refs call of commit causes wrong warning #2799
Comments
@cweber-dbs this documentation refers to all types of references (both tags and branches), not necessarily all pages returned by the API, which is covered by the pagination docs. But this is also why we have this runtime warning as it's often confusing in other endpoints. @JohnVillalovos I guess we could tweak this a bit to also supply the calling method instead if it calls |
Not an answer to this. Did the warning not indicate the file and line number in the user code that caused the warning? I thought it was supposed to do that. |
Nope, only the reference to utils.py line 199 is included:
|
Not sure if you are able to do it or not, but would be interesting if you could apply the small change to Hopefully the error message would then include the path to the calling code. Though I am surprised and confused that there is no filename at all at the end. I wonder if that could be because it is running on MacOS, which I'm guessing from seeing "homebrew" |
Description of the problem, including code/CLI snippet
Fetching the refs for a commit causes a warning. The warning is missleading due to the fact, that it provides some information for the list() method.
Expected Behavior
The warning should inform about the refs() method and not the list() method.
Actual Behavior
The following warning is shown:
Specifications
python-gitlab version: 4.4.0
API version you are using (v3/v4): ?
Gitlab server version (or gitlab.com): v16.8.1-ee
The text was updated successfully, but these errors were encountered: