I have a build that crashes LabVIEW -- it's is a known issue and not related to g-cli.
However, when LabVIEW does crash, the github action logs show a LOT of the same error message [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection. It would help tidy up the logs if this error were not duplicated so many times -- I've removed about 50 or so (duplicate) lines from the following stream of log messages:
...
20:04:43.608 [DEBUG] Comms reader stopped.
20:04:43.608 [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection
20:04:43.608 [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection
20:04:43.608 [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection
...
... ~~~ approx 50 duplicate lines removed from here ~~~
...
20:04:43.608 [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection
20:04:43.608 [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection
20:04:43.608 [ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection
20:04:43.698 [DEBUG] Signal Handler Stopped.
20:04:43.698 [DEBUG] Action loop stopped.
20:04:43.698 [DEBUG] Waiting on monitoring thread to complete
20:04:44.076 [DEBUG] Stopping LabVIEW monitoring due to stop command from application
20:04:44.076 [DEBUG] Monitoring thread completed
20:04:44.076 [DEBUG] Exiting G-CLI with exit code -1
...
Version Info:
g-cli(rust) binary -- built from e68f1f85d9b40c5c44cc53fb163c73ce207920cbIssue:
I have a build that crashes LabVIEW -- it's is a known issue and not related to g-cli.
However, when LabVIEW does crash, the github action logs show a LOT of the same error message
[ERROR] Comms Error: Unexpected EOF Error: LabVIEW has probably closed the connection. It would help tidy up the logs if this error were not duplicated so many times -- I've removed about 50 or so (duplicate) lines from the following stream of log messages: