Finally always creates error based exit #1

Open
opened 2019-01-17 21:14:23 +00:00 by sloum · 0 comments
Owner

In the init there is a finally to the try except block. That finally always exists with a code of 1. As a result, the system, in theory, always exists with a 1. Make sure this is not the case, and if it is, fix the behavior.

In the init there is a finally to the try except block. That finally always exists with a code of 1. As a result, the system, in theory, always exists with a 1. Make sure this is not the case, and if it is, fix the behavior.
sloum self-assigned this 2019-01-17 21:14:23 +00:00
sloum added the
bug
label 2019-01-17 21:15:00 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sloum/colorchat#1
No description provided.