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

757: unexpected token #490

Closed
guilhermesimoes opened this issue Nov 25, 2013 · 5 comments
Closed

757: unexpected token #490

guilhermesimoes opened this issue Nov 25, 2013 · 5 comments

Comments

@guilhermesimoes
Copy link

When using the Twitter::Streaming::Client, I get this error when the json gem tries to parse some tweets. As an example, a tweet with the id 404911776141037568 threw this error. However, I can't reproduce it by calling client.status(404911776141037568)with the Twitter::REST::Client. Is there a difference between the way a tweet is parsed with the Streaming and Rest clients?

Stack trace here.

Env Version
twitter 5.0.0.rc.1
json 1.8.1
Rails 4.0.1
Ruby 2.0.0
OS Ubuntu 12.04
@sferik
Copy link
Owner

sferik commented Nov 28, 2013

Any particular reason you’re using version 5.0.0.rc.1 instead of 5.0.0 final? Can you please try to reproduce the issue with the final gem? It would also be helpful to know the patch level of your Ruby version.

@sferik
Copy link
Owner

sferik commented Nov 28, 2013

Is there a difference between the way a tweet is parsed with the Streaming and Rest clients?

Yes and no. The as-yet-unreleased update to buftok (see #484) may resolve this issue. If upgrading to version 5.0.0 doesn’t solve it, can you try to reproduce the issue on master?

@guilhermesimoes
Copy link
Author

No particular reason, actually. I hadn't noticed you had released 5.0.0 final. Guess I should have checked, sorry. I'll upgrade to 5.0.1 (which I think you released today).

As for the Ruby patch level, I'm currently on ruby-2.0.0-p247 but I know that there was a new patch released to address some security concern, so I'll also try to upgrade to that new version.

@sferik
Copy link
Owner

sferik commented Nov 28, 2013

Please reopen this issue if 5.0.1 doesn’t fix the problem.

@sferik sferik closed this as completed Nov 28, 2013
@guilhermesimoes
Copy link
Author

Just wanted to let you know that everything's running smoothly now. 👏

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

No branches or pull requests

2 participants