[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3761: Fake client/server pair implementing proposed GBS Python interface (part 1: immutables)

[Tahoe-LAFS]

#3761: Fake client/server pair implementing proposed GBS Python interface (part 1:
immutables)
--------------------------+-----------------------------------
     Reporter:  itamarst  |      Owner:  itamarst
         Type:  task      |     Status:  new
     Priority:  normal    |  Milestone:  HTTP Storage Protocol
    Component:  unknown   |    Version:  n/a
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------------------

Comment (by itamarst):

 To go the manual audit route, given a whole bunch of arbitrary fakes:

 1. For each method in IStorageServer and related objects (bucket
 reader/writer), grep for method definitions; eventually this should
 discover all fakes.
 2. For each fake, add logic to print tracebacks(?) to file.
 3. Add logic to print tracebacks to file for real code too.
 4. Run unit and integration tests.
 5. Uniquify file.

 At this point we should have locations of all calls into Foolscap storage
 protocol, and can audit it for bad assumptions like "order of calls
 matches order of delivery".

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3761#comment:8>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage