Warn if callback takes more than a couple seconds to change to a background callback.
Open
Nobody has claimed this yet.
feature
P3
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
When an app is deployed and a callback takes more 30 seconds (default timeout for most servers), it fails with a timeout error. When in development, we should warn that callback takes too long and should be changed to a background callback.
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
The issue does not name a file, test, or entry point. Start by tracing how Dash executes callbacks in development and handles the deployed callback timeout, then determine where elapsed time can trigger a warning. Done means development reports callbacks that exceed the intended short threshold and recommends using a background callback, without changing deployed timeout behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100