Thanks, @gewarren, but I'm confused. Typically <exception/> indicates exceptions that are thrown out of a method, but in the case of OperationCanceledException, with an async / Task-returning method, it should always be stored into the resulting task.

Thanks, @gewarren, but I'm confused. Typically <exception/> indicates exceptions that are thrown out of a method, but in the case of OperationCanceledException, with an async / Task-returning method, it should always be stored into the resulting task.

@stephentoub Yes, I agree with that, but in my notes from our meeting in November this was one of the things we decided to do as a stop-gap measure. I'm happy to close this, or perhaps we can still use the <exception> tag but note that it's a stored exception? Something like:

<exception cref="T:System.OperationCanceledException">The cancellation token was canceled. This exception is stored into the returned <see cref="T:System.Threading.Tasks.Task`1" />.</exception>

perhaps we can still use the tag but note that it's a stored exception? Something like:

Did we discuss just doing that for all the exceptions, e.g. copyimg from the sync counterpart and adding that verbiage in the exception tag itself? I wonder if that'd be sufficient to just call this whole thing done.

perhaps we can still use the tag but note that it's a stored exception? Something like:

Did we discuss just doing that for all the exceptions, e.g. copying from the sync counterpart and adding that verbiage in the exception tag itself? I wonder if that'd be sufficient to just call this whole thing done.

@stephentoub We didn't discuss that, but it seems like a good idea to me. Thoughts @antonfirsov @BillWagner? We could run the tool periodically to catch any new exceptions that were added to the synchronous method.

We could run the tool periodically to catch any new exceptions that were added to the synchronous method.

I like this plan. It keeps us moving forward.

Converted to draft PR until I add in the extra text on the end.

Learn Build status updates of commit 01e30fc:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

• [Error: CannotMergeCommit] Cannot merge commit 01e30fc6ebbfd203c70c698af687c9cf2c421127 in branch operationcanceledexceptions of repository https://github.com/gewarren/dotnet-api-docs into branch main (commit 5d696e23da385cf61d686f3e8ba2f580f9723880). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

Closing and replacing due to too many conflicts.