#226 closed enhancement (fixed)
move to foolscap-0.2.2
| Reported by: | zooko | Owned by: | warner |
|---|---|---|---|
| Priority: | major | Milestone: | 0.7.0 |
| Component: | code-network | Version: | 0.7.0 |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
There's a new version of foolscap which is backwards-compatible with foolscap v0.1.7 but which adds more robust connection-setup foolscap#28. Shall we use this new version of foolscap in tahoe v0.7.0?
Change History (2)
comment:1 Changed at 2007-12-13T20:10:33Z by warner
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed at 2007-12-13T20:10:45Z by warner
- Summary changed from new improved foolscap? to move to foolscap-0.2.2
Note: See
TracTickets for help on using
tickets.
I've copied foolscap-0.2.2 (released last night) into misc/dependencies/ and updated calc-deps.py and made the necessary code changes (the logging facility that I originally developed in tahoe has been moved into foolscap, and further enhanced there).
I still need to make foolscap-0.2.2 debs for all our platforms, but all the necessary tahoe-side code is now in place.
Note that the new logging code does *not* write log events to disk by default. To see the events, you either need to connect to the logport, provide a logpublisher, or set the FLOGFILE= environment variable. The existing logs/twistd.log will get some (but not all) messages, because there is still a lot of tahoe and foolscap code that writes to twisted's logger and not to foolscap's. Foolscap logging is still very much in development; the next release will offer more ways to get at the log data (as we figure out what is actually useful).
I may make some more changes to tahoe w.r.t. logging, but nothing that needs to hold up 0.7.0, so I'm going to close this one out now.