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
Currently, closed checks are susceptible to a check-then-act race condition. While this isn't too bad (when they actually go to use the connection, there will be an error), it would be better to throw the correct Closed*SystemException. We can also close the system while operations are in progress, which is a more serious error.
Make close either block until all pending operations are complete or queue the closure, but avoid closing the connection until all pending operations are complete.
The text was updated successfully, but these errors were encountered:
bluekeyes
changed the title
Fix race conditions between close() and other methods on SSH systems
Fix close() race conditions on SSH systems
Jul 7, 2015
Remove close() implementation from BaseFileSystem because it was not
flexible enough for real use cases (see also #24).
Refactor SSH system creation to better support HostControlSystems.
Essentially, constructing any system also creates its pair, but this is
relatively lightweight because connections are shared.
Fixes#12.
Currently, closed checks are susceptible to a check-then-act race condition. While this isn't too bad (when they actually go to use the connection, there will be an error), it would be better to throw the correct
Closed*SystemException
. We can also close the system while operations are in progress, which is a more serious error.Make
close
either block until all pending operations are complete or queue the closure, but avoid closing the connection until all pending operations are complete.The text was updated successfully, but these errors were encountered: