investigate flask inotify problems
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
We've received reports of people having trouble getting Flask apps to reload with inotify. They have to fallback to the stat/polling-based reloader.
As far as I know, our flask app in the python example
https://github.com/tilt-dev/tilt-example-python/blob/master/3-recommended/app.py
uses the inotify-based reloader
I wonder if Tilt could help you diagnose when this is happening and what you need to do to fix it. Like maybe it could check the sysctl limits in the container and see if you were hitting one?
Needs some investigation and some repro steps
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Flask reload problem described in the issue, using the Python example's app.py and comparing inotify with the stat/polling-based reloader. Investigate whether container sysctl limits explain the failure, document reproducible steps, and define what diagnostic information Tilt should provide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100