-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
runserver_plus: watchdog >=2.3.* causes unwanted behavior #1805
Comments
Not sure if it's related but I am seeing some weird behavior too. Does anyone have this issue?
|
Hi @YAmikep, We have the same issue here. |
Ha right, if I pin watchdog to 2.2, I don't see the issue anymore. It might be worth filling this bug on the watchdog project then maybe? |
I don't think that's a I will try to contribute with a pull request in the next days. |
I see what you mean. Makes sense now. 👍 |
After some digging, I found out that this problem is not directly related with django-extensions, but with werkzeug. It seems that the problem has been solved on main branch, here's the related issue: pallets/werkzeug#2603. |
I have changed Werkzug to 2.2.3 and still have this issue on cookiecutter Django with Docker. local requirements below. For me only works if I start server with --- local requirements ---
|
@michal-stachura |
Hi,
We are using runserver_plus in our projects, and yesterday, we started to notice a problem on change detection. Basically, watchdog started to detect changes only by loading a page on the browser. In our investigation, we discovered that watchdog added a new feature to detect
FileOpenedEvent
which appears to trigger change detection without any actual file changes. We suspect that this new feature is causing the issue.Does this make any sense?
The text was updated successfully, but these errors were encountered: