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
So this is an i8n bug. I have a source named "vigun.iSelect-consensus-2016.gen.Muñoz-Amatriaín_Mirebrahim_2017". The data tables load fine, but the integration fails, throwing the following exception:
Caused by: org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0xf1 0x6f 0x7a 0x2d
Where: COPY tracker, line 1, column sourcename
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2433)
at org.postgresql.core.v3.QueryExecutorImpl.processCopyResults(QueryExecutorImpl.java:1114)
at org.postgresql.core.v3.QueryExecutorImpl.writeToCopy(QueryExecutorImpl.java:996)
at org.postgresql.core.v3.CopyInImpl.writeToCopy(CopyInImpl.java:35)
at org.postgresql.copy.CopyManager.copyIn(CopyManager.java:224)
at org.postgresql.copy.CopyManager.copyIn(CopyManager.java:203)
at org.intermine.dataloader.DataTracker.writeMap(DataTracker.java:551)
at org.intermine.dataloader.DataTracker.flush(DataTracker.java:404)
... 139 more
This isn't an InterMine bug per se, but it means that if we use org.postgresql.copy.CopyManager.copyIn(String, InputString) to populate the tracker table, we're not supporting international source names. (That's arguably a bug in copyIn, since 0xf1=ñ is most definitely a UTF-8 character, and that's under the JDBC package.)
The text was updated successfully, but these errors were encountered:
So this is an i8n bug. I have a source named "vigun.iSelect-consensus-2016.gen.Muñoz-Amatriaín_Mirebrahim_2017". The data tables load fine, but the integration fails, throwing the following exception:
This isn't an InterMine bug per se, but it means that if we use org.postgresql.copy.CopyManager.copyIn(String, InputString) to populate the tracker table, we're not supporting international source names. (That's arguably a bug in copyIn, since 0xf1=ñ is most definitely a UTF-8 character, and that's under the JDBC package.)
The text was updated successfully, but these errors were encountered: