move to foolscap-0.2.2 #226

New Issue

zooko · 2007-12-09T04:53:44Z

zooko commented

2007-12-09 04:53:44 +00:00

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?

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](http://foolscap.lothar.com/trac/ticket/28). Shall we use this new version of foolscap in tahoe v0.7.0?

zooko added the

labels 2007-12-09 04:53:44 +00:00

zooko added this to the 0.7.0 milestone 2007-12-09 04:53:44 +00:00

warner was assigned by zooko

2007-12-09 04:53:44 +00:00

warner commented

2007-12-13 20:10:33 +00:00

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.

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.

warner added the

fixed

label 2007-12-13 20:10:33 +00:00

warner closed this issue

2007-12-13 20:10:33 +00:00

warner changed title from ~~new improved foolscap?~~ to move to foolscap-0.2.2

2007-12-13 20:10:45 +00:00

Sign in to join this conversation.