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
{{ message }}
This repository was archived by the owner on Apr 26, 2021. It is now read-only.
Due to a bug in CCG 2.0.7, when CCG is issued a DATA REMOVE command, it returns (if successful) a code 200, rather than 201 (which is the correct response). This causes UC to wait for CCG to send more information that CCG does not send. Because reading from the socket is a blocking process, this causes UC to become unresponsive.
This is an acknowledged bug within CCG, and will be fixed in CCG 2.1: CasparCG/server#400
The text was updated successfully, but these errors were encountered:
Due to a bug in CCG 2.0.7, when CCG is issued a DATA REMOVE command, it returns (if successful) a code 200, rather than 201 (which is the correct response). This causes UC to wait for CCG to send more information that CCG does not send. Because reading from the socket is a blocking process, this causes UC to become unresponsive.
This is an acknowledged bug within CCG, and will be fixed in CCG 2.1: CasparCG/server#400
The text was updated successfully, but these errors were encountered: