Skip to content
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

Maximum semantic analysis iteration count reached error with django-stubs 5.0.3 & 5.0.4 #2373

Open
Alexerson opened this issue Sep 17, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Alexerson
Copy link
Contributor

Alexerson commented Sep 17, 2024

Bug report

What's wrong

When running django-stubs 5.0.2, mypy goes through without error. But when updating django-stubs to 5.0.3, I’m getting the following error:
error: INTERNAL ERROR: maximum semantic analysis iteration count reached.

The traceback is huge, and not really helping, so my next step is to have a minimal reproduction, but I wanted to raise the bug in case someone else is running into this as well. I’ll also try to review what’s happening between the 2 versions to understand where the issue can be.

System information

  • OS: Linux 6.10.5
  • python version:
  • django version: 5.0.9 (but same error with 5.1.1)
  • mypy version: 1.11.2 (but same error with 1.10.1)
  • django-stubs version: 5.0.3
  • django-stubs-ext version: 5.0.3

It works fine with:

  • django version 5.1.1
  • mypy version 1.11.2
  • django-stubs version 5.0.2
  • django-stubs-ext version 5.0.2
@Alexerson Alexerson added the bug Something isn't working label Sep 17, 2024
@flaeppe
Copy link
Member

flaeppe commented Sep 17, 2024

If I understand you correctly you can reproduce with the code you have? Essentially that your code triggers a regression between the versions?

Could you perhaps run a git bisect between 5.0.2 and 5.0.3 to pin point which commit introduced the issue?

You could also try out master to see if the issue exists there too.

@Alexerson
Copy link
Contributor Author

Correct. My next plan was indeed to do a git bisect but didn’t have plan to complete. Will do (hopefully) today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants