Skip to content

Use AsyncTask thread-safe logging in GetMicrosoftNuGetPackagesMap#11948

Draft
jonathanpeppers with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-finder-use-thread-safe-logmessage
Draft

Use AsyncTask thread-safe logging in GetMicrosoftNuGetPackagesMap#11948
jonathanpeppers with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-finder-use-thread-safe-logmessage

Conversation

Copilot AI commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

GetMicrosoftNuGetPackagesMap runs on AsyncTask's background execution path but still logged through the obsolete Log property. This updates the task to use the thread-safe logging helper intended for AsyncTask implementations.

  • Logging path

    • Replace the direct Log.LogMessage (...) call in GetMicrosoftNuGetPackagesMap.RunTaskAsync () with the inherited LogMessage (...) helper.
    • Keep the existing message text and exception handling behavior unchanged.
  • Scope

    • Limit the change to the single background-thread logging site in GetMicrosoftNuGetPackagesMap.cs.
    • Leave task behavior, outputs, and cache handling untouched.
} catch (Exception ex) {
	LogMessage ("Could not download microsoft-packages.json: {0}", ex.Message);
}

Co-authored-by: jonathanpeppers <840039+jonathanpeppers@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix usage of obsolete Log property in GetMicrosoftNuGetPackagesMap Use AsyncTask thread-safe logging in GetMicrosoftNuGetPackagesMap Jul 2, 2026
Copilot AI requested a review from jonathanpeppers July 2, 2026 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[fix-finder] Use thread-safe LogMessage() helper instead of obsolete Log property in GetMicrosoftNuGetPackagesMap

2 participants