Azure / Azure/azure-openai-benchmark
Value for MAX_RETRY_SECONDS should not be hardcoded
Open
- Dominant language
- Python
- Stars
- 154
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the value of MAX_RETRY_SECONDS is hardcoded in code,
It would be a good idea to make this value configurable.
Relates to - [#33 ](https://github.com/Azure/azure-openai-benchmark/issues/33)
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the code that defines and uses MAX_RETRY_SECONDS, then inspect how other runtime values are configured. Determine the appropriate configuration entry point and verify that changing it affects retry behavior without relying on the hardcoded value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100