Skip to content

Conversation

@pascal-nordic
Copy link
Contributor

The exception displayed in case there is a timeout when trying to identify what type of communication to have with the device is not user-friendly. This PR look to improve it.

identify what type of communication to have with the device is not
user-friendly. This PR look to improve it.

Signed-off-by: Pascal Hernandez <pascal.hernandez@nordicsemi.no>
@pascal-nordic pascal-nordic self-assigned this Jan 9, 2026
Copy link

@gregersrygg gregersrygg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for improving the error handling 👍 It's nice to catch errors, but this doesn't make the error messages more understandable for the users as far as I can tell. It just prints the error message without the full stacktrace. It's also only catching TimeoutErrors. Is that the only type of error? Wouldn't there be a different error if the user has another terminal connected to the device? I run into that problem very often.
Also, I recommend doing this within detect_shell_mode or to make a util function so this logic only needs to be maintained one place.

@pascal-nordic
Copy link
Contributor Author

@gregersrygg I will handle the error inside the function that detect the shell mode. I'm closing this PR

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.

3 participants