Page MenuHomePhabricator

[services] Lib - fix bugs in ClientWriteReactorBase
ClosedPublic

Authored by karol on Jun 15 2022, 3:08 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jul 5, 2:12 PM
Unknown Object (File)
Fri, Jul 5, 8:36 AM
Unknown Object (File)
Thu, Jul 4, 9:46 PM
Unknown Object (File)
Thu, Jul 4, 10:37 AM
Unknown Object (File)
Tue, Jul 2, 6:32 AM
Unknown Object (File)
Mon, Jul 1, 2:00 AM
Unknown Object (File)
Wed, Jun 26, 7:13 AM
Unknown Object (File)
Wed, Jun 26, 7:13 AM

Details

Summary

Depends on D4252

I spotted some obvious bugs in this class. They've not been spotted before because the compilation doesn't see them. I guess it's because we do not yet use this class.

Test Plan

None really. It doesn't affect the compilation, but I wanted to make these two right so if we ever use this class, it will be better.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

karol edited the test plan for this revision. (Show Details)
karol added a reviewer: tomek.

I guess it's because we do not yet use this class.

More accurately, it's because the test plan for the diff that initially committed this class was insufficient.

When you put a diff up, you should have a plan to test that code. If you have code that you haven't had a chance to test yet, you should not be putting that code up for review. It's better to wait a bit before putting up a stack of diffs (until you have tested it) then you put up untested code, and later come back and revise it after you've tested.

By testing code you save your reviewers time, reduce churn, and make sure we aren't launching broken features.

What can we do to avoid having code that not compiles in the codebase?

This revision is now accepted and ready to land.Jun 20 2022, 5:39 AM
karol edited the summary of this revision. (Show Details)

retrigger CI

I understand.

Things we can do now:

  • abandon this diff
  • remove this class and write it again when it's needed
  • land this
  • land this and add a comment/failing assert saying that the code's not been tested

I'd land it. It is true this is not tested but if we ever need this class, a lot of work already will be done.

throw that this class is not tested

I added an error that this class is not tested, if you feel like we should do something different here, please, let me know