StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1876122
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-09T19:09:55.557
FavoriteCount
0
LastActivityDate
2009-12-09T19:09:55.557
LastEditDate
LastEditorUserId
0
OwnerUserId
6309
ParentId
1875306
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Is this a python-related issue like the one described in <a href="http://www.mail-archive.com/fab-user@nongnu.org/msg00853.html" rel="nofollow noreferrer">this thread</a>? <blockquote> The main problem with this is that the <code>stdout</code>/<code>stderr</code> capturing is per-run/sudo invocation and not per-task. It would be wonderful if you could explain me how I could collect outputand error by only modifying the file called <code>fabfile_runner.py</code>. Idealy the fabric task itself could be unmodified, this would allow to upload the the factory the same file that you have tested manually. Check out the Fabric source and look in the 'tests' folder, specifically tests/utils.py. It contains a single decorator, <code>@mock_streams</code>, which is capable of wrapping a function (any function in any Python code -- it's not Fabric specific, as I mentioned) and redirecting <code>sys.stdout</code> and/or <code>sys.stderr</code> for capture/examination. It's designed for use around functions, being a decorator, so you could use it directly by modifying your <code>fabfile_runner.py</code> like so: </blockquote> fabfile_runner.py <pre><code>from StringIO import StringIO import sys from test_fabfile import hello_world def execute(task): output = StringIO() error = StringIO() sys.stdout = output sys.stderr = error task() sys.stdout = sys.__stdout__ sys.stderr = sys.__stderr__ return (output.getvalue(), error.getvalue()) output, error = execute(hello_world) print "output : %s" %output print "error : %s" %error </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFabric error: Fatal error: local() encountered an error (return code 2) while executing 'git commit -m 'message'
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.