New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A start at a HTTP-based storage server and client #1161
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good so far, some inline comments
@@ -95,7 +95,7 @@ EOF | |||
propagatedBuildInputs = with python.pkgs; [ | |||
twisted foolscap zfec appdirs | |||
setuptoolsTrial pyasn1 zope_interface | |||
service-identity pyyaml magic-wormhole treq |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this why nixos is failing? (we still use treq
right?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's missing different things in 19.whatever and 20.whatever. Maybe we can drop the former...
Co-authored-by: Jean-Paul Calderone <exarkun@twistedmatrix.com>
…away any day now.
…s/tahoe-lafs into 3843-start-http-storage-server
Fixes https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3843
Fixes https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3762 (basically "we return the same thing as Foolscap").