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
Interestingly, I'm only seeing that error when I run my smoketest. When I use my Rails app, it logs the BOM to the file directly without complaint. That is to say, the log file has BOM characters throughout, but for some reason only when logging from a running Rails app.
Either way, it shouldn't have BOM characters scattered throughout the file.
One possible fix is to open the log file as 8-bit ASCII. For example, in the weirdly-named LogHelper.rb:
I tried to trace through why Ruby is making any of the decisions it made around this string (opening the file as UTF-8, converting from ASCII to UTF-8, etc.) but got lost around io.c's make_writeconv.
Perhaps the better solution is to convert respXml.body to UTF-8 sooner, just before logging it, in api_transaction.rb:
I have this
LogConfig.yml
:I'm seeing this error:
Expanding it further:
That's a UTF-8 BOM that it's trying to log.
Interestingly, I'm only seeing that error when I run my smoketest. When I use my Rails app, it logs the BOM to the file directly without complaint. That is to say, the log file has BOM characters throughout, but for some reason only when logging from a running Rails app.
Either way, it shouldn't have BOM characters scattered throughout the file.
One possible fix is to open the log file as 8-bit ASCII. For example, in the weirdly-named
LogHelper.rb
:I tried to trace through why Ruby is making any of the decisions it made around this string (opening the file as UTF-8, converting from ASCII to UTF-8, etc.) but got lost around io.c's
make_writeconv
.Perhaps the better solution is to convert
respXml.body
to UTF-8 sooner, just before logging it, inapi_transaction.rb
:The text was updated successfully, but these errors were encountered: