Make `cpu_time_per_second` agnostic for `Unlimited - *` plans
Open
- Dominant language
- Python
- Stars
- 562
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
Customers on Unlimited plans should not face the "Daily Usage Limit Reached" errors if they are running resource heavy jobs which consumes a lot of cpu time consumed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing where `cpu_time_per_second` is evaluated for `Unlimited - *` plans and where the "Daily Usage Limit Reached" error is generated. Confirm the existing behavior for other plans, then verify that resource-heavy jobs on Unlimited plans no longer trigger this error while applicable limits remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100