New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add try/catch around FindWorkspace calls to handle FileNotFound #1387
Conversation
@jmarolf Please take a look |
} | ||
catch (FileNotFoundException fex) | ||
{ | ||
logger.LogError(fex.Message); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't we show a message saying we couldn't find the file instead of logging an error? Doesn't this still show a stack trace to the user?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We log the message because the workspace finder throws this exception with different messages based on how it fails. This does not log the stack trace.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should rework this to not rely on exception handling but wanted to address the regression.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since this is in main
I am ok with waiting for a full re-work. do we want this to go into the 6.x branch instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing out wrong base branch. Updated to release/6.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alright, I'll email .NET Tactics to see if they want to take this for .NET 6
Azure Pipelines successfully started running 2 pipeline(s). |
Resolves #1386