Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

debug json parsing errors on valid json #620

Closed
devth opened this issue Jan 20, 2017 · 1 comment
Closed

debug json parsing errors on valid json #620

devth opened this issue Jan 20, 2017 · 1 comment

Comments

@devth
Copy link
Member

devth commented Jan 20, 2017

e.g.

!json http://www.earthcam.com/cams/common/gethofitems.php?hofsource=com&tm=ecn&camera=nationalmall&start=43&length=21&ec_favorite=0&cdn=0

:cop: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('' (code 65279 / 0xfeff)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: java.io.StringReader@70c0b38a; line: 1, column: 2] :cop:
jkieberk pushed a commit to jkieberk/yetibot that referenced this issue Mar 25, 2017
@jkieberking
Fix For Issue yetibot#620
0575552 
-Idea from: mmazi/rescu#54 (comment)

Not sure if this is something that clj-http should be stripping out
on their end? This might just be a hack, and there is a better way
to go about this?

Also, adding [cheshire] as a dependency might fix it as well, although when I
tried that, it still gave the same error (cheshire is a dependency
of clj-http when using the :as :json feature of clj-http/get
see [here](https://github.com/dakrone/clj-http#optional-dependencies) )
jkieberk pushed a commit to jkieberk/yetibot that referenced this issue Mar 25, 2017
@jkieberking
Revert "Fix For Issue yetibot#620"
6a3264d 
Woops, forgot to put this in a new branch
jkieberk pushed a commit to jkieberk/yetibot that referenced this issue Mar 25, 2017
@jkieberking
Fix For Issue yetibot#620
6fa24c6 
-Idea from: mmazi/rescu#54

Not sure if this is something that clj-http should be stripping out
on their end? This might just be a hack, and there is a better way
to go about this?

Also, adding [cheshire] as a dependency might fix it as well, although when I
tried that, it still gave the same error (cheshire is a dependency
of clj-http when using the :as :json feature of clj-http/get
see [here](https://github.com/dakrone/clj-http#optional-dependencies) )
jkieberk pushed a commit to jkieberk/yetibot that referenced this issue Mar 25, 2017
@jkieberking
Fix For Issue yetibot#620
196c41f 
-Idea from: mmazi/rescu#54

Not sure if this is something that clj-http should be stripping out
on their end? This might just be a hack, and there is a better way
to go about this?

Also, adding [cheshire] as a dependency might fix it as well, although when I
tried that, it still gave the same error (cheshire is a dependency
of clj-http when using the :as :json feature of clj-http/get
see [here](https://github.com/dakrone/clj-http#optional-dependencies) )
devth added a commit that referenced this issue Mar 26, 2017
@devth
Merge pull request #647 from jkieberk/json-parse-error
066b1e5 
Fix For Issue #620
@devth
Copy link
Member Author

devth commented Apr 6, 2017

Fixed by #647

@devth devth closed this as completed Apr 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@devth