[BUG]: Incorrect parameters in resource loc.messages.UnexpectedDbghelpdllExpected0Actual1 of task PublishSymbolsV2 #21627
Description
New issue checklist
- I searched for existing GitHub issues
- I read pipeline troubleshooting guide
- I checked how to collect logs
Task name
PublishSymbolsV2
Task version
master
Issue Description
In file:
the message:
loc.messages.UnexpectedDbghelpdllExpected0Actual1
has the value:
"Library dbghelp.dll is already loaded from an unexpected path. Expected '{0}'. Actual '{0}'."
where the second parameter value should be {1} instead of {0} like so:
"Library dbghelp.dll is already loaded from an unexpected path. Expected '{0}'. Actual '{1}'."
This is the same issue reported 6 months ago in #21074 and not fixed, closed by inactivity by a bot. FWIW, I find it annoying and frustrating that in the era of Microsoft copilots everywhere such a simple bug is not fixed in a couple of minutes, even automatically by a copilot agent. I spend more time lately debugging problems in Microsoft stuff due to misleading or error messages with missing information that the time that copilots save me while coding.
Environment type (Please select at least one enviroment where you face this issue)
- Self-Hosted
- Microsoft Hosted
- VMSS Pool
- Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 2025
Relevant log output
##[warning]Library dbghelp.dll is already loaded from an unexpected path. Expected 'D:\a\_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.264.0\dbghelp.dll'. Actual 'D:\a\_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.264.0\dbghelp.dll'.
(notice that both paths are the same because of this bug)Full task logs with system.debug enabled
No response