Singly API timing out--returning non-valid JSON #122

erictj opened this Issue Jul 7, 2012 · 1 comment


None yet

2 participants


Seeing this in our logs this morning.

When I try to hit the offending endpoint directly,

I get this (incomplete JSON):

            "created_at":"Sat Jul 07 14:20:04 +0000 2012",
            "text":"Craving some smart,
             eclectic reading on creativity? Start here:",
            "source":"<a href=\"\" rel=\"nofollow\">Buffer</a>",
                "name":"Maria Popova",
                "description":"Interestingness hunter-gatherer obsessed with combinatorial creativity. Editor of @brainpickings & @explorer. Bylines for @WiredUK & @TheAtlantic. MIT Fellow.",
                "created_at":"Tue Oct 02 14:18:16 +0000 2007",
                "time_zone":"Eastern Time (US & Canada)",
        "q":" book pickings",
            "description":"Steal Like an Artist: 10 Things Nobody Told You About Being Creative Austin Kleon Some time ago,
             artist and writer Austin Kleon - one of my favorite thinkers,
             a keen observer of and participant in the creative economy of the digital age - was invited to give a talk to students,
             the backbone for which was a list of 10 things he wished he'd heard as a young creator.",
            "title":"book pickings",

Ok, this is fixed, I turned on streaming last night so that it'd start sending json right away for large result sets and when it encountered an error (from a typo) mid-stream it barfed, doh!

@quartzjer quartzjer closed this Jul 7, 2012
@jerbob92 jerbob92 pushed a commit to jerbob92/hallway-original that referenced this issue Nov 10, 2013
@quartzjer quartzjer fix a typo, number is not a function, of course, related to Singly/AP… 73d3bce
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment