Align LinuxStrategy async pattern with WindowsStrategy #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LinuxStrategyusedExecute()withTask.Run()wrapper whileWindowsStrategyimplementedExecuteAsync()directly, creating inconsistent async patterns across platform strategies.Changes
LinuxStrategy.cs: Replace
Execute()+Task.Run()with nativeExecuteAsync()implementationTask.Run()wrapperWindowsStrategy)GeneralUpdateBootstrap.cs: Fix compilation error from previous commit
GetOption(UpdateOption.DownloadTimeOut)result to avoid duplicate calls0as default, notnull)Both platform strategies now follow identical async patterns:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.