-
Notifications
You must be signed in to change notification settings - Fork 7
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
Encoding error at holdings endpoint #1041
Comments
This is the bug:
I can observe the records coming in from Faraday as ascii-8bit but I can't get a fixture to work for a test. Rails is too good at preferring utf-8 at every step along the way. |
hackartisan
added a commit
that referenced
this issue
Feb 4, 2021
hackartisan
added a commit
that referenced
this issue
Feb 8, 2021
hackartisan
added a commit
that referenced
this issue
Feb 22, 2021
hackartisan
added a commit
that referenced
this issue
Mar 15, 2021
hackartisan
added a commit
that referenced
this issue
Mar 22, 2021
hackartisan
added a commit
that referenced
this issue
Mar 29, 2021
hackartisan
added a commit
that referenced
this issue
Apr 12, 2021
hackartisan
added a commit
that referenced
this issue
May 3, 2021
hackartisan
added a commit
that referenced
this issue
Jun 7, 2021
hackartisan
added a commit
that referenced
this issue
Jul 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://app.honeybadger.io/projects/54497/faults/74869729/c27c2aae-6572-11eb-91cc-3d3c1a6d177d#notice-summary
Accesing this same mmsid at endpoints using alma-rb don't have the same issue. It would be nice to push holdings up to that gem. For now I'll likely just force the encoding.
The text was updated successfully, but these errors were encountered: