-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Task.Delay correction of the maximum valid delay #8035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The maximum delay of the Task.Delay method is documented to be Int32.MaxValue, but the actual maximum is 0xFFFFFFFE (4294967294). dotnet/runtime#68818 This affects the .NET 6 and later versions. On previous .NET versions the documented maximum value is correct.
Tagging subscribers to this area: @dotnet/area-system-threading-tasks Issue DetailsSummaryThe maximum delay of the This affects the .NET 6 and later versions. On previous .NET versions the currently documented maximum value is correct. Fixes #68818
|
Docs Build status updates of commit f2d8f37: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
This comment was marked as outdated.
This comment was marked as outdated.
Docs Build status updates of commit ae149a1: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Thanks @theodorzoulias |
Summary
The maximum delay of the
Task.Delay
method is documented to beInt32.MaxValue
(2147483647), but the actual maximum is0xFFFFFFFE
(4294967294).This affects the .NET 6 and later versions. On previous .NET versions the currently documented maximum value is correct.
Fixes #68818