173.consume tahoe lafs eliot logs by exarkun · Pull Request #174 · gridsync/gridsync

and others added 30 commits

March 26, 2019 08:45
This will fail more loudly (hopefully with an AttributeError) if Tahoe itself
changes somehow.

Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
But give it a default so Tahoe API doesn't change.

Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
already a transitive dependency via twisted
Provide a better fake reactor.  Mock doesn't know when to call startConnecting
and I'd rather not duplicate that logic in the test method itself.
MemoryReactorClock knows to do this and it fixes the problem with starting
then stopping the TCP4ClientEndpoint.
Tahoe.restart just calls Tahoe.start which gets the right API auth token.
Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
repeat yourseeeeeelf

Co-authored-by: Chris Wood <chris@leastauthority.com>
Co-authored-by: Chris Wood <chris@leastauthority.com>
Otherwise it tries to stop it
So that it connects to the right address
Pass just the information we need to the start call, instead.
Noticed when listenTCP actually raised an exception and forced us to notice
the except statement used an undefined name.

exarkun

@exarkun

@exarkun

pytest will load them for us automatically and so we won't need the
flake8-upsetting imports from test_tahoe in test_streamedlogs.

also importing library code from test modules is sad.

@exarkun

@exarkun

also avoid even importing the global reactor until it is being used
future improvement would probably be to use the reactor attribute