Page MenuHomePhabricator

Allow PhutilChannels to have their write channels closed explicitly
ClosedPublic

Authored by epriestley on Nov 10 2013, 11:28 PM.
Tags
None
Referenced Files
F14110235: D7552.diff
Wed, Nov 27, 4:40 PM
Unknown Object (File)
Tue, Nov 12, 9:25 AM
Unknown Object (File)
Tue, Nov 12, 6:11 AM
Unknown Object (File)
Oct 24 2024, 5:42 AM
Unknown Object (File)
Oct 23 2024, 9:54 PM
Unknown Object (File)
Oct 17 2024, 4:44 AM
Unknown Object (File)
Oct 16 2024, 7:10 AM
Unknown Object (File)
Oct 3 2024, 11:41 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
Restricted Maniphest Task
Commits
rPHU3ef0937680ad: Allow PhutilChannels to have their write channels closed explicitly
Summary

Ref T2230. This simplifies some tests and cleans up some TODOs in the hosting stuff. See testCloseExecWriteChannel for an example of where we need this in practice.

Test Plan

Ran unit tests; commented out the closeWriteChannel() calls and got test failures instead of hangs.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

epriestley updated this revision to Unknown Object (????).Nov 10 2013, 11:35 PM
  • Also fix an issue with reading remaining messages off a channel after it has closed but before its buffer has emptied.
epriestley updated this revision to Unknown Object (????).Nov 10 2013, 11:36 PM
  • Fix return type.