-
Notifications
You must be signed in to change notification settings - Fork 3
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
Make sure that even exception does not abort progress bar rendering on the middle #222
Milestone
Comments
Also see my suggestion here. |
aeqz
added a commit
that referenced
this issue
Jan 23, 2023
Problem: It seems that the current progress bar rendering action is not completely protected against exceptions. Solution: As it is an action that runs for a short amount of time and we really want it to not be interrputed, we can wrap it with uninterruptibleMask. The resulting rendering loop also gets simpler with this change.
8 tasks
aeqz
added a commit
that referenced
this issue
Jan 27, 2023
Problem: It seems that the current progress bar rendering action is not completely protected against exceptions. Solution: As it is an action that runs for a short amount of time and we really want it to not be interrputed, we can wrap it with uninterruptibleMask. The resulting rendering loop also gets simpler with this change.
aeqz
added a commit
that referenced
this issue
Feb 1, 2023
Problem: It seems that the current progress bar rendering action is not completely protected against exceptions. Solution: As it is an action that runs for a short amount of time and we really want it to not be interrputed, we can wrap it with uninterruptibleMask. The resulting rendering loop also gets simpler with this change.
aeqz
added a commit
that referenced
this issue
Aug 31, 2023
Problem: It seems that the current progress bar rendering action is not completely protected against exceptions. Solution: As it is an action that runs for a short amount of time and we really want it to not be interrputed, we can wrap it with uninterruptibleMask. The resulting rendering loop also gets simpler with this change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clarification and motivation
In #163 we have fixed the progress bar rendering thread to never abort in the middle of printing disregard when the links verification has finished. Now the terminal is not supposed to periodically appear in some weird state after
xrefcheck
completes.However in case of an async exception (it may be a
UserInterrupt
which we now handle), AFAIS we still let the progress bar to be rendered partially, and this seems to be as bad as having a not cleaned up resource.Acceptance criteria
^C
should still abort the application immediately.The text was updated successfully, but these errors were encountered: