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.

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

Explore "exhausted input" errors #152

Open
chuwy opened this issue Sep 21, 2020 · 0 comments
Open

Explore "exhausted input" errors #152

chuwy opened this issue Sep 21, 2020 · 0 comments
Labels

Comments

@chuwy
Copy link
Contributor

chuwy commented Sep 21, 2020

I've seen this several times in test environments, but never paid any attention. Recently I saw it for the first time in production pipeline and now we have OSS user mentioning it: https://discourse.snowplowanalytics.com/t/bad-enrichment-invalid-json-exhausted-input/4253

This message comes from circe when it cannot parse a string into valid Json, usually because server responded with empty or truncated string.

However, I'm not sure that this is actually circe's problem - very likey the culprit is the HTTP cilent we use (scalaj) or actual Iglu Server, although I've never seen this with json4s (pre-0.6.0 Iglu clilent)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant