summaryrefslogtreecommitdiffstats
path: root/tests/test_manifest_xml.py
diff options
context:
space:
mode:
authorJosh Steadmon <steadmon@google.com>2022-03-08 10:24:43 -0800
committerJosh Steadmon <steadmon@google.com>2022-03-16 17:33:07 +0000
commit244c9a71a689743acea97c6a07ff4dfce4dc6dab (patch)
tree2a52943292478722db03174e577f05ab4ffc1eb7 /tests/test_manifest_xml.py
parentb308db1e2a982ae4158cb6fedd23d3d547bd09b0 (diff)
downloadgit-repo-244c9a71a689743acea97c6a07ff4dfce4dc6dab.tar.gz
trace: allow writing traces to a socket
Git can write trace2 events to a Unix domain socket [1]. This can be specified via Git's `trace2.eventTarget` config option, which we read to determine where to log our own trace2 events. Currently, if the Git config specifies a socket as the trace2 target, we fail to log any traces. Fix this by adding support for writing to a Unix domain socket, following the same specification that Git supports. [1]: https://git-scm.com/docs/api-trace2#_enabling_a_target Change-Id: I928bc22ba04fba603a9132eb055141845fa48ab2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/332339 Reviewed-by: Raman Tenneti <rtenneti@google.com> Reviewed-by: Mike Frysinger <vapier@google.com> Tested-by: Josh Steadmon <steadmon@google.com>
Diffstat (limited to 'tests/test_manifest_xml.py')
0 files changed, 0 insertions, 0 deletions