You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2025. It is now read-only.
Just wondering if you are still supporting this magnificent gem?
I'm using it for my app: http://topstack.io, but just hit a massive bug, where response could not be parsed as it was encoded in ASCII not UTF8.
I guess it could just be my environments reading the response as ASCII, instead of UTF8. For now I've forced it to encode in UTF8 and submitted a pull request if others have this problem: #25
Cheers,
The text was updated successfully, but these errors were encountered:
stefan-lz
changed the title
Is this gem still being actively supported?
Is this gem still being actively supported? (JSON parse bug)
Jul 3, 2014
Hi Stefan - I never really gave this gem the maintenance it needed when I first released it and since I've not actively been developing against it there's a few different bugs/issues I've not fixed.
I'm planning on rewriting a v2 of the gem over the summer with support for the write API as well, probably simplifying some of the internals as I go along.
Hi Thomas,
Just wondering if you are still supporting this magnificent gem?
I'm using it for my app: http://topstack.io, but just hit a massive bug, where response could not be parsed as it was encoded in ASCII not UTF8.
I guess it could just be my environments reading the response as ASCII, instead of UTF8. For now I've forced it to encode in UTF8 and submitted a pull request if others have this problem: #25
Cheers,
The text was updated successfully, but these errors were encountered: