summaryrefslogtreecommitdiff
path: root/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn')
-rw-r--r--doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn
new file mode 100644
index 000000000..00a4c2237
--- /dev/null
+++ b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn
@@ -0,0 +1,18 @@
+What steps will reproduce the problem?
+
+ $ git annex -j sync | json_reformat
+
+What is the expected output? What do you see instead?
+
+Expecting valid JSON, instead this happens:
+
+ $ git annex -j sync | json_reformat
+ lexical error: invalid char in json text.
+ {"command":"commit","file":""# On branch master nothing to c
+ (right here) ------^
+ $
+
+
+What version of git-annex are you using? On what operating system?
+
+Newest standalone (3.20121126), Linux i386. The "json_reformat" program is from the "yajl-tools" .deb package.