On Sun, Jun 17, 2012 at 11:49 PM, Brent Tubbs <[email protected]>wrote:
> Hello Fabric users and devs,
>
> I'm working on a deployment orchestration tool that uses Celery workers to
> execute Fabric tasks. The actual functionality is going great, but the log
> output from remote commands is a bit wonky; it's printed with just one
> character per line. See http://pastebin.com/0SW99xL8 for an example.
>
> I've confirmed that with the old line buffering behavior from Fabric <=0.9
> I can get normally-formatted responses in my Celery worker logs. (Example
> with a dummy project/task: http://pastebin.com/Y7jAhEqq.) So, a couple
> questions:
>
> 1. Where in the codebase is the best place to look to re-enable line
> buffering? Is there just one place, or would I have to patch a bunch of
> stuff all over?
>
> Did you saw ? I believe it does what you need.
http://docs.fabfile.org/en/1.4.0/usage/fab.html#cmdoption--linewise
>
> 1. Would a env.buffer_lines option be of interest to upstream or
> anyone else, or should I anticipate keeping this as my own
> fork/monkeypatch?
>
> As I said above the flag is already in the codebase. I'm not 100% sure how
it's executed but i'm pretty sure it's stored in env just like any other
variables in fabric. So try it as I think you don't need a patch at all. Do
keep in mind it has some limitations
http://docs.fabfile.org/en/1.4.0/usage/parallel.html#linewise-output which
is why it was turned off by default
> I appreciate your help,
> Brent
>
>
>
> ---------
>
> *Brent Tubbs*
>
>
>
> [image: YouGovPolimetrix]
>
> 285 Hamilton Avenue
> Suite #200
>
> Palo Alto, CA 94301
>
> [email protected]
>
> http://www.yougov.com/
>
>
>
>
>
>
> _______________________________________________
> Fab-user mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/fab-user
>
>
<<[email protected]>>
_______________________________________________
Fab-user mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/fab-user