You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Even in case of exceptions we never render the terminal partially.
Double ^C should still abort the application immediately.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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.
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: