Description of dapr.io/app-max-concurrency default value behavior is wrong
- Dominant language
- SCSS
- Stars
- 1k
- Forks
- 794
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 7
Description
**Describe the issue**
Description of the annotation "dapr.io/app-max-concurrency" default value says "Default value: -1, meaning no concurrency." Default value = -1 seems right, but it does not seem to mean no concurrency, but rather unlimited concurrency or no concurrency limit, as stated in this other page (https://docs.dapr.io/operations/configuration/control-concurrency/), as well as in the code here: https://github.com/dapr/dapr/blob/2adc6ae91b7138d1c7567a2655083698451b9605/cmd/daprd/options/options.go#L150
**URL of the docs**
https://docs.dapr.io/reference/arguments-annotations-overview/
**Expected content**
Correct description of the default concurrency model
**Screenshots**
Contributor guide
Research direction
Open the annotation entry for "dapr.io/app-max-concurrency" on the arguments and annotations overview page, then compare its default-value wording with the control-concurrency documentation and the referenced options.go line. Update the description to accurately explain the default concurrency model and verify the rendered documentation page.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100