-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fixes texane/stlink#780 #812
Conversation
As my comment before, I think in the upper layers we should catch the error -1 and exit (or retry with exponential backoff using rescan). I think a different implementation is necessary for that. Do you feel to fix this or leave it as is ? |
Sorry for being unresponsive for that long time. I had had many distractions and I still have. Current workaround works for me but it is apparently a dirty hack and needs to be improved as you suggested. I'm willing to implement the proper solution ASAP. |
@ceremcem: Thx for your contribution. Could you target the develop branch for that PR? Also I see that this bring up an old discussion on the backend. Can we be sure in the meanwhile that this does not break anything currently working? |
Sure thing.
I'll take extreme caution on this. |
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.
I agree that we should not be calling exit() here. This will result in undesired behavior for projects that embed libstlink. We do need to get a better understanding of how returning -1 here affects the higher layers.
@ceremcem: This PR will be closed in 3 days, should there be no further feedback. |
Hi! I'm on this one at last. Any fix would need a test case in order to prevent any breakage in the higher layers. What would you recommend? Should I write |
Can you just use |
Closed by PR #913. |
No description provided.