JSON Encoding change?

Joe Keeley's Avatar

Joe Keeley

20 Feb, 2013 07:55 PM

Was there by any chance a change to JSON encoding with the migration last night? Seeing intermittent problems with the JSON coming from LH (it's valid, but our encoder is having trouble with it) and having a really hard time narrowing it down.

  1. 1 Posted by Julien on 20 Feb, 2013 08:32 PM

    Julien's Avatar

    Hi Joe,

    Can you show me the kind of errors you're seeing? What language/library are you using?

    Thanks.

  2. 2 Posted by Joe Keeley on 20 Feb, 2013 09:24 PM

    Joe Keeley's Avatar

    UPDATE: Discovered what the problem is. When we request tickets from the API, we are getting a "points" attribute twice for each ticket in the response JSON. The parser on our end apparently has a bug and crashes sometimes with this (but not consistently). Is this intentional to have "points" in the ticket info twice?

  3. 3 Posted by Julien on 20 Feb, 2013 09:26 PM

    Julien's Avatar

    Hi Joe,

    This is most definitely a bug. Points should even be in there.. We'll get that fixed ASAP.

  4. 4 Posted by Joe Keeley on 20 Feb, 2013 09:28 PM

    Joe Keeley's Avatar

    Much appreciated - thank you!

  5. 5 Posted by Julien on 21 Feb, 2013 12:18 AM

    Julien's Avatar

    Hi Joe,

    This should be fixed now.

  6. 6 Posted by Joe Keeley on 21 Feb, 2013 05:00 PM

    Joe Keeley's Avatar

    Working great now - thanks for the quick turnaround!

  7. Joe Keeley closed this discussion on 21 Feb, 2013 05:00 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac