# A seeming rough spot, with a workaround of sorts **URL:** \ **Category:** Ansible Project\ **Tags:** ansible-project\ **Created:** [February 28, 2013, 8:37pm UTC](https://forum.ansible.com/t/a-seeming-rough-spot-with-a-workaround-of-sorts/12435 "2013-02-28T20:37:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [February 28, 2013, 8:37pm UTC](https://forum.ansible.com/t/a-seeming-rough-spot-with-a-workaround-of-sorts/12435/1 "2013-02-28T20:37:22Z")
Yeah it's not intended, but that's also the first I've heard of it. We should fix that, thanks for the heads up! Can you file a github ticket for this? We can modify our JSON parsing to start at the first "{" and it would bypass this problem, though there may also be some cleaner solutions people can think of. ---
**Author:** ![drcabana](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@drcabana](https://forum.ansible.com/u/drcabana)\ **Post date:** [March 2, 2013, 1:47am UTC](https://forum.ansible.com/t/a-seeming-rough-spot-with-a-workaround-of-sorts/12435/2 "2013-03-02T01:47:01Z")
I have opened a github ticket. Thanks for the quick response. drc ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [March 2, 2013, 2:52am UTC](https://forum.ansible.com/t/a-seeming-rough-spot-with-a-workaround-of-sorts/12435/3 "2013-03-02T02:52:19Z")
Ok, so I misread. This isn't breaking parsing, it's breaking native scp and sftp, and has been reported as early as 2005. There isn't much we can do here, but I have increased the logging if you are using Paramiko, so at least it will tell you "Garbage packet recieved" now.