After ctrl-c, stdout appears to be swallowed

Description

The following was done withOUT the fix for SYNR-1125. I.e., we have not introduced the mechanism to check for keyboard interrupt:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 > library(synapser) # disconnect wifi > synLogin() ^C ^C ^C # reconnect wifi > > 1+1 > message("foo") foo > 1+1 > cat("foo\n") > stop("foo") Error: foo

Operations like "1+1" and "cat('foo\n')" have no output, while operations like "message('foo')" and "stop('foo')" do have output. I think the former use stdout and the latter stderr. We have logic to capture stdout and stderr while calling Python methods. I wonder if hitting ctrl+c while this reroute is active is leaving stdout permanently modified.

I have also seen this after hitting ctrl+c while downloading a large file (i.e., while 'synGet' was waiting to complete).

Environment

None

Status

Assignee

Unassigned

Reporter

Bruce Hoff

Labels

None

Validator

Kimyen Truong

Release Version History

None

Fix versions

Priority

Major
Configure