Conversation
before fix, order of arguments mattered: - unless /diag is last argument, it is ignored; and the following argument is swalloed silently /diag /l gv.log -> diagnostic switch is ignored, no log file is created /l console /diag -> diagnostic output is emitted to console /l gv.log /diag -> diagnostic output is emitted to log file
|
|
Thank you @davidjenni for your contribution! |
|
@davidjenni thanks for taking the time to debug this |
|
Thank you so much for fixing this @davidjenni! Should we perhaps update the documentation for this as well? |
I think he was suggesting that #4539 (comment) |
Indeed!
Yes, please! 😊 🙏🏼 |
|
🎉 This issue has been resolved in version 6.5.1 🎉 Your GitReleaseManager bot 📦🚀 |
Description
Fix to accept
/diagswitch in any argument position on cmd line, not just the last argument position.Related Issues
Resolves #4763
It also addresses the root cause of #4395 but also improves mitigation for #4539
Motivation and Context
Discovered when debugging issue #4539 (diag flag not working). While this is not the root cause for 4539, without the fix in this PR, possible workarounds for 4539 are more brittle.
How Has This Been Tested?
added unit tests to arg parser suite.
Screenshots (if appropriate):
Checklist: