-
Notifications
You must be signed in to change notification settings - Fork 42
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
[change] Adjust or remove strict test #90
Labels
Comments
Agree with that. I have installed a controller in a local network without internet and had to disable it. |
Maybe we could simply remove it to simplify our life. |
We could convert this to use system checks. This way it would be run only when the We could also issue a warning instead of an error. |
devkapilbansal
added a commit
that referenced
this issue
Oct 13, 2021
devkapilbansal
added a commit
that referenced
this issue
Oct 13, 2021
devkapilbansal
added a commit
that referenced
this issue
Oct 13, 2021
devkapilbansal
added a commit
that referenced
this issue
Oct 13, 2021
devkapilbansal
added a commit
that referenced
this issue
Oct 15, 2021
nemesifier
pushed a commit
that referenced
this issue
Oct 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This strict test feature is backfiring quite a bit.
It's triggered every time django is initialized, also with scripts, management commands, celery, etc.
We should address this, maybe we can turn this into a management command to execute only some times.
The text was updated successfully, but these errors were encountered: