-
Notifications
You must be signed in to change notification settings - Fork 16
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
0.5.12: regression EdgeCaseError: astAssign.targets[0] is of type <class 'ast.Subscript'> #190
Comments
Update: it seems this this problem originates from another place, probably a dependency of pydoclint that was recently released is causing it. It does reproduce with last releases and multiple versions of python too. |
Thanks for reporting! Let me try to reproduce this error with your repo. |
Locally I no longer can run pydoclint due to the raised bug and I tried on two different machines: macos and ubuntu, both arm64 and using python installed using mise. Still, as you probably seen, on CI it works. I am starting to suspect something related to either pre-commit, uv or mise being involved here. |
Hi @ssbarnea , I was unable to reproduce this issue locally either. Could you try it in a fresh local env? Or could you find out which line of code in the repo caused this issue? (If you look further than "Traceback (most recent call last)" there may be such info?) |
I am also recently running into this issue, despite not changing my pydoclint version (0.5.7). It is fine in CI and when I run |
I probably need more information to reproduce this issue, because when I ran ansible-dev-tools locally, I saw no errors. |
This is the PR where I had the issue: XRPLF/xrpl-py#749 Reproduction:
Running on Mac M1 |
Hi @mvadari , I tried your steps, and I still couldn't see the issue. So the issue may be some dependencies in your existing environment clashes with pydoclint. And the reason why things work in CI (as well as on my computer) is that every time pydoclint is run in a fresh environment. (When I run it on your repo on my computer, it's in fresh environments also.) |
I am unable to reproduce on linux but on macos m1 seems to happen with any python blend i tried. I kinda doubt is its dependencies as it runs via pre-commit with only these:
I was failing on a file that was not even tracked under git, part of a test venv,
I removed the folder and now is passing, still I am sure that the issue is real. Sadly, too late as I removed the folder. |
@jsh9 I had this issue with a fresh install too (I also thought it might be some other dependency). Seems like based on @ssbarnea's comment that it's at least a Mac (if not M1)-specific issue. |
OK, so I found the issue thanks to @ssbarnea 's clue ( I have a PR to fix it. That said, an separate (orthogonal) issue is: why on your local machines would your test framework ( |
The PR is merged, and the change will be shipped with the new version (0.5.13), which will come out in a few hours. (I have another thing to include into the new version.) |
0.5.13 is published to pypi. |
The fix works for me now, thanks! |
While trying to update from 0.5.9 to 0.5.12, i faced a runtime exception on https://github.com/ansible/ansible-dev-tools repository.
I am still trying to figure out what is causing it as the output is not really very useful.
The text was updated successfully, but these errors were encountered: