denoland / denoland/deploy_feedback
More information for CPU time exceeded crashes
Open
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Once in a while I have CPU time exceeded errors:
I think it would be great to have more info about the context of these errors, like the http request uri, backtrace, etc in order to detect the slow code.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reproducing a CPU time exceeded error and identify where its current error context is assembled; done means the error exposes useful request information and a backtrace for diagnosing slow code.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100